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

Support npm 3+ #2006

Merged
merged 9 commits into from
Aug 9, 2019
Merged

Support npm 3+ #2006

merged 9 commits into from
Aug 9, 2019

Conversation

cdebost
Copy link
Collaborator

@cdebost cdebost commented Jan 31, 2019

This is a partial application of #1928 which contains only changes needed for npm 3 support. #1928 its sister PRs in mr and mop introduced too many changes to review all at once.

See montagejs/mr#145 for details on how this impacts existing apps.

@cdebost cdebost force-pushed the feature/npm3 branch 3 times, most recently from 0ef1468 to c606787 Compare January 31, 2019 20:50
@cdebost cdebost mentioned this pull request Jan 31, 2019
@cdebost cdebost requested review from johnnykahalawai, tejaede and marchant and removed request for marchant, johnnykahalawai and tejaede February 1, 2019 03:17
If they can't be loaded from the app package, they will be retried under
mr (npm 2 / legacy bundling support).
I suspect this code only exists for historical reasons, but it seems
totally unnecessary, as bluebird will already be cached in the registry
and will not be loaded twice. The hardcoded bluebird path causes an
extra 404 when loading the app with npm 3+.
@marchant
Copy link
Member

marchant commented Aug 9, 2019

Tested across multiple projects with the matching mr PR. Merging.

@marchant marchant merged commit 9dcf38f into master Aug 9, 2019
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.

2 participants