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
As mentioned in the docs. Once a deployment is triggered, the build container will receive a request that there is a job available. And the build container is a Docker container that uses an Amazon Linux based image.
Why are the node_modules for a Next.js project in the vercel build container totally different from what you would get if you installed on a normal machine?
I made a quick patch on start-server.js but can't seem to find it in the node_modules of the Vercel build container after deployment. There's no start-server.js
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Question
As mentioned in the docs. Once a deployment is triggered, the build container will receive a request that there is a job available. And the build container is a Docker container that uses an Amazon Linux based image.
Why are the node_modules for a Next.js project in the vercel build container totally different from what you would get if you installed on a normal machine?
I made a quick patch on
start-server.js
but can't seem to find it in the node_modules of the Vercel build container after deployment. There's nostart-server.js
Also, I didn't find any public dir.
Beta Was this translation helpful? Give feedback.
All reactions