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
I'm working on a project where client and server live in the same git repo, (would like to) use the same package.json, etc. I read the documentation on the subject, which didn't mention calling the dev server from the parent of the folder it all lives in.
For example: node client/build/dev-server.js
I've spent a few hours mucking around with paths and whatnot and I've settled in just throwing a cd into the package.json scripts for now, but eventually I want to use concurrently to run the server and client together, and I can't do that in that case.
The pain points:
Can't manually specify location of /source,
Have to go through and change relative directory of dev-client.js in webpack.dev.conf.js
Have to manually change webpack entry and aliases
After all this, and hacing changed every path I could find, the production build succeeds but the dev server fails, with an empty error no less! It's just blank.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
I'm working on a project where client and server live in the same git repo, (would like to) use the same package.json, etc. I read the documentation on the subject, which didn't mention calling the dev server from the parent of the folder it all lives in.
For example:
node client/build/dev-server.js
I've spent a few hours mucking around with paths and whatnot and I've settled in just throwing a
cd
into the package.json scripts for now, but eventually I want to use concurrently to run the server and client together, and I can't do that in that case.The pain points:
/source
,The text was updated successfully, but these errors were encountered: