-
Notifications
You must be signed in to change notification settings - Fork 64
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
Use prepack instead of prepublish #389
Conversation
`prepublish` is no longer the correct way to build before `publish`. The correct script to use is `prepack`. The reason for this is that `prepublish` runs after `pack` and before `publish`, and `pack` is the script which defines what is published during `publish`, i.e., the package being published is already created by the time `prepublish` is called. By building in `prepack` the package will be created properly during `pack` and then published during `publish`. Using `prepublish` relies on having an already-done, possibly stale build.
sounds good, thanks for the PR! not sure what CI is yapping about. @ikatyang? |
We use |
Yep, that appears to have fixed it! |
Thanks! |
So, yarn is mandatory if I want to use @types/ramda ? |
No, see Usage. |
Yes, but when performing
|
Ah, sorry. I didn't notice that'll trigger the
|
@ikatyang would it possibly be best to change the |
Actually, the problem is that we don't need to |
I don't know all the considerations for yarn, but I think recent npm releases did fix much of their original issues. |
prepublish
is no longer the correct way to build beforepublish
. The correct script to use isprepack
. The reason for this is thatprepublish
runs afterpack
and beforepublish
, andpack
is the script which defines what is published duringpublish
, i.e., the package being published is already created by the timeprepublish
is called. By building inprepack
the package will be created properly duringpack
and then published duringpublish
. Usingprepublish
relies on having an already-done, possibly stale build.