question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Errors when creating new Quasar project

See original GitHub issue

Describe the bug There are problems when creating new quasar project. Eslint is reporting missing or not found types / functions / etc even they are imported and are working correctly.

Codepen/jsFiddle/Codesandbox (required) Just create new project quasar create <name> with typescript

To Reproduce Steps to reproduce the behavior:

  1. Create new project
  2. Look at the console

Expected behavior No errors

Screenshots link link2

OS: MacOS 11 Node: 14.15.5 NPM: 6.14.11 Yarn: 1.22.10

Additional context I created different project, maybe week ago and its working properly. No idea what changed

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:11 (6 by maintainers)

github_iconTop GitHub Comments

4reactions
capuvillacommented, Aug 27, 2021

still showing errors to start new projects, both in version 1 and version 2

3reactions
jean-moldovancommented, Aug 11, 2021

Also seeing some typescript related errors on the application start:

[webpack-dev-server] import/named: PropType not found in 'vue'
[webpack-dev-server] import/named: ActionTree not found in 'vuex'

and similar.

I’m on the latest quasar:

  "dependencies": {
    "@quasar/extras": "^1.10.10",
    "axios": "^0.21.1",
    "core-js": "^3.16.1",
    "dayjs": "^1.10.6",
    "quasar": "^2.0.3",
    "vue-i18n": "^9.0.0-beta.0",
    "vuex": "^4.0.1"
  },
  "devDependencies": {
    "@babel/eslint-parser": "^7.15.0",
    "@quasar/app": "^3.0.4",
    "@types/node": "^16.4.13",
    "@typescript-eslint/eslint-plugin": "^4.29.1",
    "@typescript-eslint/parser": "^4.29.1",
    "eslint": "^7.32.0",
    "eslint-config-standard": "^16.0.3",
    "eslint-plugin-import": "^2.24.0",
    "eslint-plugin-node": "^11.1.0",
    "eslint-plugin-promise": "^5.1.0",
    "eslint-plugin-vue": "^7.16.0",
    "npm-check-updates": "^11.8.3",
    "stylelint": "^13.13.1",
    "stylelint-config-standard": "^22.0.0"
  },

Removing and reinstalling node_modules did not help.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Problem with creating new project , dev not running
Hi all , i made installation ,see bellow, if i run dev nothing happend. Please help , im newcomer in quasar . Installation...
Read more >
node.js - I am getting this error when trying to create a project ...
node. js - I am getting this error when trying to create a project with Quasar CLI 'zsh: command not found: quasar' -...
Read more >
Commands List | Quasar Framework
Familiarize yourself with the list of available commands inside a Quasar project: $ quasar Example usage $ quasar <command> <options> Help for a...
Read more >
Upgrading to Quasar V2 - Dependencies, Removing CLI ...
We'll start going through the guide, and run into some upgrade errors along the way!...This gives me a chance to share some Vue3...
Read more >
Getting Started with the Quasar Framework - Section.io
To create a new Quasar app, run the command below. ​. $ quasar create hello-world-app. hello-world-app will be the name of your project....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found