Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when create nuxt-app #805

Closed
matamune94 opened this issue Jun 29, 2021 · 1 comment · Fixed by #806
Closed

Error when create nuxt-app #805

matamune94 opened this issue Jun 29, 2021 · 1 comment · Fixed by #806
Assignees

Comments

@matamune94
Copy link

Error like below and lost plugin, middleware, asset, folders

create-nuxt-app v3.7.0
✨  Generating Nuxt.js project in truyenxy
? Project name: truyenxy
? Programming language: JavaScript 
? Package manager: Yarn
? UI framework: Tailwind CSS
? Nuxt.js modules: Axios - Promise based HTTP client
? Linting tools: ESLint, Prettier    
? Testing framework: None
? Rendering mode: Universal (SSR / SSG)
? Deployment target: Server (Node.js hosting)
? Development tools: jsconfig.json (Recommended for VS Code if you're not using typescript)
? Continuous integration: None
? Version control system: Git
warning nuxt > @nuxt/babel-preset-app > core-js@2.6.12: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8  
engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual v 
ersion of core-js.
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less depende 
ncies.
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > chokidar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure bina 
ries. Upgrade to fsevents 2.
yarn run v1.22.4
$ eslint --ext ".js,.vue" --ignore-path .gitignore . --fix

C:\Users\Admin\Desktop\manga_snowbox\truyenxy_frontend_v2\truyenxy\.eslintrc.js
  0:0  error  Parsing error: No Babel config file detected for C:\Users\Admin\Desktop\manga_snowbox\truyenxy_frontend_v2\truyenxy\.eslintrc.js. Either disable config file 
checking with requireConfigFile: false, or configure Babel so that it can find the config files

C:\Users\Admin\Desktop\manga_snowbox\truyenxy_frontend_v2\truyenxy\components\NuxtLogo.vue
  0:0  error  Parsing error: No Babel config file detected for C:\Users\Admin\Desktop\manga_snowbox\truyenxy_frontend_v2\truyenxy\components\NuxtLogo.vue. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files

C:\Users\Admin\Desktop\manga_snowbox\truyenxy_frontend_v2\truyenxy\components\Tutorial.vue
  0:0  error  Parsing error: No Babel config file detected for C:\Users\Admin\Desktop\manga_snowbox\truyenxy_frontend_v2\truyenxy\components\Tutorial.vue. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files

C:\Users\Admin\Desktop\manga_snowbox\truyenxy_frontend_v2\truyenxy\nuxt.config.js
  0:0  error  Parsing error: No Babel config file detected for C:\Users\Admin\Desktop\manga_snowbox\truyenxy_frontend_v2\truyenxy\nuxt.config.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files

C:\Users\Admin\Desktop\manga_snowbox\truyenxy_frontend_v2\truyenxy\pages\index.vue
  0:0  error  Parsing error: No Babel config file detected for C:\Users\Admin\Desktop\manga_snowbox\truyenxy_frontend_v2\truyenxy\pages\index.vue. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files

✖ 5 problems (5 errors, 0 warnings)
@clarkdo
Copy link
Member

clarkdo commented Jun 29, 2021

v3.7.1 has been published.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants