Support "resolutions" in typescript libraries
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 183
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Currently only the local package.json is copied into the build directory. Because the workspace global package.json (with it's resolutions fields) is missing package resolution behaves different to outside of leeway.
One way to "fix" this would be to add a config workspaceRootPackageJson and merge that into the local package.json.
/cc @akosyakov
Contributor guide
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 locating the build logic that copies the local package.json into the build directory, then inspect how the workspace root package.json is handled. Done means TypeScript library package resolution honors the workspace package.json resolutions fields as it does outside leeway.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100