Add yarn constraints rules requiring that dual CJS/ESM builds and type declarations be exposed for all export subpaths in package manifests
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 413
- Forks
- 308
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 253
Description
## Descriptions
- Adapt [these rules](https://github.com/MetaMask/core/pull/4648/files#diff-594447fef9feecf11f1839e337c464b7b857fdb73fde7e18940eaa9cdf5b819dR496-R518) so that they are applied to all subpath exports, not just `'exports["."]'`.
- Fix package manifests that violate the new rules.
- https://github.com/MetaMask/core/blob/main/packages/notification-services-controller/package.json
- https://github.com/MetaMask/core/blob/main/packages/profile-sync-controller/package.json
## References
- Follow-up from https://github.com/MetaMask/core/pull/4648
- See https://github.com/MetaMask/core/pull/4648#discussion_r1758671441
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 existing rules in pull request 4648 and compare them with all export subpaths in the package manifests. Update the rules to require dual CJS/ESM builds and type declarations for each subpath, then fix notification-services-controller/package.json and profile-sync-controller/package.json until the constraints pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100