Closed lianginx closed 1 year ago
@lianginx I'm also faced same issue when developping. I have fixed bellow steps:
rm -rf node-modules
rm yarn.lock
yarn
@lianginx I have tested again with the following commands:
# remove old files
rm -rf node_modules .nuxt .output yarn.lock
# build & production preview
yarn && yarn build && yarn preview
# production
docker-compose up -d # Start and run in the background.
docker-compose down # Stop and delete
It works fine in my environment.
@lianginx I have tested again with the following commands:
# remove old files rm -rf node_modules .nuxt .output yarn.lock # build & production preview yarn && yarn build && yarn preview # production docker-compose up -d # Start and run in the background. docker-compose down # Stop and delete
It works fine in my environment.
This method is effective, thank you very much. It seems that a bad influence was caused by the historical file.
I found an issue, after running
yarn build
,node .output/server/index.mjs
will throw an error.Originally posted by @lianginx in https://github.com/lianginx/chatgpt-nuxt/issues/13#issuecomment-1549020478