Warn about missing file specified in `exports` `main` `module` `types`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 432
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Describe the feature
Just migrated from unbuild (with ext: 'js'), I almost forgot to change .[jt]s in the package to .m[jt]s.
If a non-existent file is referenced in the exports` `main` `module` `types of package.json, a warning after building may enhance DX.
Additional information
- Would you be willing to help implement this feature?
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 tracing how package.json fields named in the issue—exports, main, module, and types—are read during the build. Identify the validation or reporting entry point and add coverage for a referenced file that does not exist; done means the build warns about the missing file without changing valid package behavior.
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