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
The setup instructions said to run npm run build on the extracted release files
Actual behavior
npm ERR! enoent ENOENT: no such file or directory, open 'C:\atlas2-14-1\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
Steps to reproduce behavior
Following the setup guide.
At the moment I've removed the npm run build step from the setup guide, but I'm unclear on the intended behavior. The current release zip includes the node_modules folder and can be copied directly to the web server, but is there a bundling/minification step that's now missing with the current release? I noticed that the browser makes hundreds of requests to load javascript and other resources.
The text was updated successfully, but these errors were encountered:
Expected behavior
The setup instructions said to run
npm run build
on the extracted release filesActual behavior
Steps to reproduce behavior
Following the setup guide.
At the moment I've removed the
npm run build
step from the setup guide, but I'm unclear on the intended behavior. The current release zip includes thenode_modules
folder and can be copied directly to the web server, but is there a bundling/minification step that's now missing with the current release? I noticed that the browser makes hundreds of requests to load javascript and other resources.The text was updated successfully, but these errors were encountered: