You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modules are only whitelisted in webpack nodeExternals if manually specified in nuxt.config.js.
What is actually happening?
Modules are always whitelisted in webpack nodeExternals if they contain a "." in their path.
Additional comments?
One side-effect of this behaviour is, that the package from node_modules is re-executed whenever the bundle is re-executed.
That is once per SSR-request in devMode, since the default for runInNewContext is then set to true.
The re-execution produces a new Instance of the plugin, which effectively disables the Vue.js internal check if the Plugin has already been installed.
Since the Vue module is not re-executed, the Plugin is then installed multiple times, which can lead to secondary, Plugin-dependent Bugs.
In case of @sum.cumo/vue-states the Plugin (unsuccessfully) tried to redefine a property on a component once per installation.
This bug report is available on Nuxt community (#c10729)
The text was updated successfully, but these errors were encountered:
Version
v2.12.2
Reproduction link
https://github.com/JohannesLamberts/nuxt-bug-externals-whitelist
Steps to reproduce
Follow steps from https://github.com/JohannesLamberts/nuxt-bug-externals-whitelist/blob/master/README.md
What is expected ?
Modules are only whitelisted in webpack nodeExternals if manually specified in nuxt.config.js.
What is actually happening?
Modules are always whitelisted in webpack nodeExternals if they contain a "." in their path.
Additional comments?
One side-effect of this behaviour is, that the package from node_modules is re-executed whenever the bundle is re-executed.
That is once per SSR-request in devMode, since the default for runInNewContext is then set to
true
.The re-execution produces a new Instance of the plugin, which effectively disables the Vue.js internal check if the Plugin has already been installed.
Since the Vue module is not re-executed, the Plugin is then installed multiple times, which can lead to secondary, Plugin-dependent Bugs.
In case of
@sum.cumo/vue-states
the Plugin (unsuccessfully) tried to redefine a property on a component once per installation.The text was updated successfully, but these errors were encountered: