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

fix(preinstall): run preinstall before reify #2713

Closed
wants to merge 1 commit into from

Conversation

wraithgar
Copy link
Member

This puts the preinstall life cycle script where it belongs,
i.e. before the actual installation/reify has taken place.

References

Found during research for #2690

This puts the preinstall life cycle script where it belongs,
i.e. before the actual installation/reify has taken place.
@wraithgar wraithgar requested a review from a team as a code owner February 16, 2021 22:08
@wraithgar wraithgar added Release 7.x work is associated with a specific npm 7 release release: next These items should be addressed in the next release labels Feb 16, 2021
@wraithgar
Copy link
Member Author

Historical context on why it is like this is because apparently people complained that dependencies weren't available during preinstall

@wraithgar wraithgar added Needs Discussion is pending a discussion and removed release: next These items should be addressed in the next release labels Feb 17, 2021
@ljharb
Copy link
Collaborator

ljharb commented Feb 17, 2021

I’m confused, how could any dependencies be available pre install?

@wraithgar
Copy link
Member Author

I’m confused, how could any dependencies be available pre install?

They can't. I don't know why this was changed to accommodate that but because it was we have a tougher decision.

This may need to be thrown on the "Fix the life cycle scripts for real" pile that would constitute a major change.

@ljharb
Copy link
Collaborator

ljharb commented Feb 17, 2021

ahhh i get it, that's the reason that the default branch is the way it is; this PR fixes that.

LGTM :-)

@wraithgar
Copy link
Member Author

Closing this as the change is a breaking one and this needs to be ironed out in a new "what are even lifecycle events" to happen after we have actually documented all the lifecycle events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Discussion is pending a discussion Release 7.x work is associated with a specific npm 7 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants