Skip to content
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.

Improvements to the Neutrino 9 migration UX #1160

Merged
merged 2 commits into from
Oct 9, 2018
Merged

Improvements to the Neutrino 9 migration UX #1160

merged 2 commits into from
Oct 9, 2018

Conversation

edmorley
Copy link
Member

@edmorley edmorley commented Oct 9, 2018

  • An error is now shown when using the links HTML option without also specifying a custom template, so that users affected by html-template: Replace html-webpack-template with our own template #1049 know what changes they need to make. See:
    Neutrino 9 beta/release candidate feedback #1129 (comment)
  • The migration guide now recommends regenerating the lockfiles.
  • The migration section about supported Node.js versions has been made clearer. See:
    Neutrino 9 beta/release candidate feedback #1129 (comment)
  • The neutrino bin script error message now mentions test being removed, includes --mode for the inspect example, and uses the correct URL for the migration guide.
  • The minify.image option deprecation error message no longer refers to @neutrinojs/image-minify, since it was removed. I've linked to the issue since it gives more background as to why compile-time minification is not recommended.
  • The hotEntries option deprecation check now always occurs, and not only when options.hot is enabled. A test has also been added.

@edmorley edmorley added the bug label Oct 9, 2018
@edmorley edmorley added this to the v9 milestone Oct 9, 2018
@edmorley edmorley self-assigned this Oct 9, 2018
@edmorley edmorley added the docs label Oct 9, 2018
@edmorley edmorley requested a review from eliperelman October 9, 2018 14:30
Copy link
Member

@eliperelman eliperelman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r+ with nits addressed.

@@ -39,12 +39,15 @@ neutrino --inspect --mode production > v9.config
git diff --no-index v8.config v9.config
```

Please [file an issue](https://github.com/neutrinojs/neutrino/issues) if any issue arises from upgrade
that may not be outlined here.
**We strongly recommend that any Yarn/NPM lockfiles (eg `yarn.lock` or `package-lock.json`) are
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: "npm" is lowercase.

throw new Error(
'The default Neutrino HTML template no longer supports the "links" option. ' +
'To set a favicon use the "favicon" option instead. For stylesheets either ' +
'import the equivalent NPM package from JS, or if using a CDN is preferred, ' +
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: s/NPM/npm

* An error is now shown when using the `links` HTML option without
  also specifying a custom template, so that users affected by #1049
  know what changes they need to make. See:
  #1129 (comment)
* The migration guide now recommends regenerating the lockfiles.
* The migration section about supported Node.js versions has been made
  clearer. See:
  #1129 (comment)
* The `neutrino` bin script error message now mentions `test` being
  removed, includes `--mode` for the inspect example, and uses the
  correct URL for the migration guide.
* The `minify.image` option deprecation error message no longer refers
  to `@neutrinojs/image-minify`, since it was removed. I've linked
  to the issue since it gives more background as to why compile-time
  minification is not recommended.
* The `hotEntries` option deprecation check now always occurs, and not
  only when `options.hot` is enabled. A test has also been added.
* Cleans up a few more `t.throws()` usages (missed in #1159).
@edmorley edmorley merged commit ff2f696 into neutrinojs:master Oct 9, 2018
@edmorley edmorley deleted the migration-ux-tweaks branch October 9, 2018 18:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

Successfully merging this pull request may close these issues.

2 participants