[Bug report] Errors on Nuxt stage with new NodeJS
See original GitHub issueHow to reproduce the behaviour
Since commit 0cabdcee1ee1ab96c3ed3654b5efeed9a5f25bca up to current master
I have tones of similar errors on building Doccano (via production docker-compose) on Nuxt stage:
$ git checkout 0cabdcee1ee1ab96c3ed3654b5efeed9a5f25bca
$ /opt/docker-compose -f docker-compose.prod.yml up --build
<...>
ERROR in ./components/containers/annotation/TextClassification.vue?vue&type=script&lang=js& (./node_modules/babel-loader/lib??ref--2-0!./node_modules/vuetify-loader/lib/loader.js??ref--17-0!./node_modules/vue-loader/lib??vue-loader-option
s!./components/containers/annotation/TextClassification.vue?vue&type=script&lang=js&)
Module not found: Error: Can't resolve 'core-js/modules/es6.array.find' in '/app/components/containers/annotation'
@ ./components/containers/annotation/TextClassification.vue?vue&type=script&lang=js& (./node_modules/babel-loader/lib??ref--2-0!./node_modules/vuetify-loader/lib/loader.js??ref--17-0!./node_modules/vue-loader/lib??vue-loader-options!./co
mponents/containers/annotation/TextClassification.vue?vue&type=script&lang=js&) 4:0-40
@ ./components/containers/annotation/TextClassification.vue?vue&type=script&lang=js&
@ ./components/containers/annotation/TextClassification.vue
@ ./node_modules/babel-loader/lib??ref--2-0!./node_modules/vuetify-loader/lib/loader.js??ref--17-0!./node_modules/vue-loader/lib??vue-loader-options!./pages/projects/_id/text-classification/index.vue?vue&type=script&lang=js&
@ ./pages/projects/_id/text-classification/index.vue?vue&type=script&lang=js&
@ ./pages/projects/_id/text-classification/index.vue
@ ./.nuxt/router.js
@ ./.nuxt/index.js
@ ./.nuxt/client.js
@ multi ./.nuxt/client.js
Your Environment
- Operating System: Ubuntu 18.04.2 LTS
- Python Version Used: system-wide Python is 3.6.8 but how is it used?
- When you install doccano: 0cabdcee1ee1ab96c3ed3654b5efeed9a5f25bca
- How did you install doccano (Heroku button etc):
$ /opt/docker-compose -f docker-compose.prod.yml up --build
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Node.js v17.0.0 - Error starting project in development mode ...
After updating Node.js to the new version, when starting the project in development mode, the following error is obtained in the terminal.
Read more >Best Practices for Node.js Error-handling - Toptal
It's Time to Handle Errors Properly Using Node. js built-in Error object is a good practice because it includes intuitive and clear information...
Read more >Setting Up Error Reporting for Node.js - Google Cloud
You can send error reports to Error Reporting from Node. js applications by using the Error Reporting library for Node. js.
Read more >I am creating a system so that users can make bug reports ...
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not...
Read more >Process | Node.js v19.3.0 Documentation
The 'beforeExit' event is emitted when Node.js empties its event loop and has no additional work to schedule. Normally, the Node.js process will...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@icoxfog417 , sorry, updated.
Yes, fixed