neutrinojs / neutrino Public
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 scoped packages under the @neutrinojs org #424
Conversation
Looks good so far, though I see quite a few neutrino-{preset,middleware}-
references still left? (eg docs and package.json repository links)
Also, what is the plan for informing existing users that they need to migrate? People relying on greenkeeper/renovate might not know there is a new package name unless we do a another release under the old package names that gives console.warn() deprecation warnings or similar.
Yeah, I'll think we will issue deprecation messages once we release v8. Fortunately we've been using peerDependencies, so it shouldn't be too big of a deal. With a major release comes breaking changes, and it should be simple enough for most to just switch packages. Regarding the references, yeah, I haven't done any docs work yet, but package.jsons should be fixed, so that's my mistake. I'll take a look. |
OK, I think I have all the references updates from docs. |
|
lol nice find! |
Updated again, but leaving out upgrading-neutrino and creating-presets since those are not really relevant to this PR. |
Yay! |
Fixes #413.