Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inputmap resolutions and pinning #134

Merged
merged 6 commits into from
Jul 13, 2022
Merged

Inputmap resolutions and pinning #134

merged 6 commits into from
Jul 13, 2022

Conversation

guybedford
Copy link
Member

@guybedford guybedford commented Jun 2, 2022

This is a work-in-progress PR for treating inputMap as an authoritative lockfile and resolution override.

There is some complexity in deconstructing it properly to distinguish custom maps from actual lock installs, but it seems like this approach may well work.

This should enable better mutation workflows with input maps including features like uninstalls and submaps.

In addition "imports" in the import map are now treated like "dependencies" in the package.json file in that they form pinned installs that are always maintained. Scopes are then always pruned to remove anything not otherwise accessible from the graph of "imports".

@guybedford guybedford changed the title wip: inputmap reconstruction Inputmap resolutions and pinning Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support "uninstalling" packages Top-level generator installs do not use resolutions object authoritatively
1 participant