oasisprotocol / oasisprotocol/oasis-sdk
ts-web: we don't validate viability of the npm packages
Open
Nobody has claimed this yet.
c:client-sdk/typescript
c:testing
- Dominant language
- Rust
- Stars
- 90
- Forks
- 35
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 5
Description
it's all complicated by the way our current release process is to get the version bump merged before we push to npm.
the value proposition is that we'd catch devDependencies problems like in #213
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the ts-web release process described in the issue, especially the version-bump-before-publish sequence, and compare the proposed validation with the devDependencies problem in issue #213. Done means the release process detects non-viable npm packages before they are published.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100