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
And including "vue-server-renderer" in the node_modules as I would imagine most people do, avoids this inconvenience, however IMO it's really nice to be able to compile system level javascript to a few javascript files (one for each process more or less... etc.)
What does the proposed API look like?
Well if the module evaluation could be done in a way that doesn't necessitate a dynamic require statements, that would be really cool. : )
The text was updated successfully, but these errors were encountered:
In your webpack config, it will throw an error about left hand side assignment because vue server renderer is defining the process.env at runtime
In build.dev.js
What problem does this feature solve?
Webpack or likely any other bundler/compiler/sequencer is not going to be able to resolve dynamic require statements:
Example Added in comments (and at fiddle)
Hence the webpack warning:
https://github.com/vuejs/vue/blob/dev/packages/vue-server-renderer/build.dev.js#L9295
Using:
And including "vue-server-renderer" in the node_modules as I would imagine most people do, avoids this inconvenience, however IMO it's really nice to be able to compile system level javascript to a few javascript files (one for each process more or less... etc.)
What does the proposed API look like?
Well if the module evaluation could be done in a way that doesn't necessitate a dynamic require statements, that would be really cool. : )
The text was updated successfully, but these errors were encountered: