I had this problem as well. I fixed it by deleting node_modules and running npm install.

No idea, but feel free to keep investigating and maybe make some PRs if needed to support what you are doing. That’s the beauty of Open Source Software

@steffanhalv

Do NOT change the webpack target prop. It is already configured in the right way. If you need to change it you’re doing something wrong. Please also note there’s one webpack config for the renderer process and ANOTHER separate one for the main process. Which one are you trying to change? In 99% of the cases, you don’t need to change it anyway.

I see that you are importing the http package, which is a node specific library, which is NOT isomorphic (doesn’t also works being run in a browser). You could use it in the main process though, but not in the renderer.

Like I mentioned in a previous post, node-loader and it’s webpack rule for renderer process (it’s currently specified only for the main process) will be available by default in Quasar CLI v0.16.2.

Thank you all!

Please, if you have any suggestion to improve the app, don’t hesitate to report it here (or on Github)!