@metamask/providers@17.2.1 has a reference to `src` folder which is omitted in npm package
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 268
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
Our typescript setup fails because of this. This was not the case in 17.2.0.
References to `src` are in files:
- @metamask/providers/dist/initializeInpageProvider.d.cts:1:22
- @metamask/providers/dist/MetaMaskInpageProvider.d.cts:1:22
- @metamask/providers/dist/StreamProvider.d.cts:1:22
You can also see this at npm
https://www.npmjs.com/package/@metamask/providers/v/17.2.1?activeTab=code
https://www.npmjs.com/package/@metamask/providers/v/17.2.0?activeTab=code
```ts
///
```
was added at the beginning of the above files in the latest package.
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
Compare the published @metamask/providers 17.2.1 and 17.2.0 package contents, focusing on the three listed .d.cts files and their ../src/readable-stream.d.ts references. Inspect how these declarations are generated or packaged, then verify that the published declarations no longer reference omitted src files and that the TypeScript setup succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100