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
{{ message }}
This repository was archived by the owner on Mar 31, 2020. It is now read-only.
When running a newly instantiated simple template and opening it in a browser, it fails to load and an error in the console complains about exports not being defined in react-sharedb/lib/index.js.
I tracked it down to the webpack config not compiling node_modules dependencies by default, resulting in this error, because AFAIK exports only exists in Node and not in browsers.
Adding @startupjs/react-sharedb to forceCompileModules in webpack.web.config.js solves the problem, but I wonder if it wouldn't make more sense for react-sharedb's lib folder to be directly useable in a browser.
The text was updated successfully, but these errors were encountered:
I also noticed a similar issue with the routing template, causing a parsing error in webpack. This problem is caused by the pug templates in @startupjs/app. Adding the module to forceCompileModules also fixes the error.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When running a newly instantiated simple template and opening it in a browser, it fails to load and an error in the console complains about
exports
not being defined inreact-sharedb/lib/index.js
.I tracked it down to the webpack config not compiling
node_modules
dependencies by default, resulting in this error, because AFAIKexports
only exists in Node and not in browsers.Adding
@startupjs/react-sharedb
toforceCompileModules
inwebpack.web.config.js
solves the problem, but I wonder if it wouldn't make more sense forreact-sharedb
'slib
folder to be directly useable in a browser.The text was updated successfully, but these errors were encountered: