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

docs: mention caveat about missing plugins when in legacy config #3857

Merged
merged 2 commits into from Jun 22, 2019

Conversation

LinusBorg
Copy link
Member

@LinusBorg LinusBorg commented Apr 20, 2019

We don't include some plugins during legacy build when building in modern mode. Trying to tap into their options causes webpack-chain to throw a pretty cryptic error.

This warning should help people deal with that situation.


close #3845

@LinusBorg LinusBorg changed the title docs: mention caveat about missing plugins docs: mention caveat about missing plugins when in legacy config Apr 20, 2019
@@ -89,6 +89,12 @@ Vue CLI uses two environment variables to communicate this:
**Important:** These variables are only accessible when/after `chainWebpack()` and `configureWebpack()` functions are evaluated, (so not directly in the `vue.config.js` module's root scope). That means it's also available in the postcss config file.
:::

::: warning Caveat: Adjusting webpack plugins
Some Plugins, i.e. `html-webpack-plugin`, `preload-plugin` etc. are only included in the config for modern mode. Trying to tap into their options in the legacy config can s an error as the plugins don't exist.
Copy link
Member

Choose a reason for hiding this comment

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

can s an error - what does s stands for here? 😅

Copy link
Member Author

@LinusBorg LinusBorg Jun 22, 2019

Choose a reason for hiding this comment

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

Good question, I can't exactly recall but I think it would have been something like "throw an error".

that's what this sentence is about, will change it.

Copy link
Member

@NataliaTepluhina NataliaTepluhina left a comment

Choose a reason for hiding this comment

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

Thanks for adding this warning, @LinusBorg! I think it's really useful 👍
Added a minor grammar comment 😅

@NataliaTepluhina NataliaTepluhina merged commit 09ce29f into dev Jun 22, 2019
sodatea pushed a commit that referenced this pull request Jun 24, 2019
* docs: mention caveat about missing plugins
when in legacy config
close #3845

* Update browser-compatibility.md

(cherry picked from commit 09ce29f)
@LinusBorg LinusBorg deleted the feature/modern-mode-plugin-docs_issue3845 branch July 28, 2019 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

--modern flag fails when tapping into preload plugin options
2 participants