search

quasarframework / quasar

Quasar Framework - Build high-performance VueJS user interfaces in record time
https://quasar.dev
MIT License
25.52k stars 3.45k forks source link

Quasar app is not working on Windows 10 #3965

Closed averri closed 5 years ago

averri commented 5 years ago

Software version

PS C:\Users\ealverr\goodluck> quasar info

Operating System                Windows_NT(10.0.16299) - win32/x64
NodeJs                          10.15.3

Global packages
  NPM                           6.4.1
  yarn                          1.15.2
  @quasar/cli                   1.0.0-beta.4
  cordova                       Not installed

Quasar App Extensions None installed

What did you get as the error?

The command quasar dev is not recognized.

Detailed steps

PS C:\Users\ealverr> quasar create goodluck -b dev
  ___
 / _ \ _   _  __ _ ___  __ _ _ __
| | | | | | |/ _` / __|/ _` | '__|
| |_| | |_| | (_| \__ \ (_| | |
 \__\_\\__,_|\__,_|___/\__,_|_|

? Project name (internal usage for dev) goodluck
? Project product name (official name; must start with a letter if you will build mobile apps) Quasar App
? Project description A Quasar Framework app
? Author ealverr
? Check the features needed for your project: (Press <space> to select, <a> to toggle all, <i> to invert selection)ESLint
? Pick an ESLint preset Standard
? Cordova id (disregard if not building mobile apps) org.cordova.quasar.app
? Should we run `npm install` for you after the project has been created? (recommended) yarn

  Quasar CLI · Generated "goodluck".

 [*] Installing project dependencies ...

yarn install v1.15.2
info No lockfile found.
[1/5] Validating package.json...
[2/5] Resolving packages...
warning @quasar/app > workbox-webpack-plugin > workbox-build > joi@14.3.1: This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning @quasar/app > workbox-webpack-plugin > workbox-build > joi > topo@3.0.3: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning @quasar/app > workbox-webpack-plugin > workbox-build > joi > hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning @quasar/app > workbox-webpack-plugin > workbox-build > joi > topo > hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning Resolution field "ajv@6.8.1" is incompatible with requested version "ajv@^6.9.1"
warning Resolution field "ajv@6.8.1" is incompatible with requested version "ajv@^6.9.1"
[3/5] Fetching packages...
info fsevents@1.2.8: The platform "win32" is incompatible with this module.
info "fsevents@1.2.8" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning "@quasar/app > babel-loader@8.0.5" has unmet peer dependency "@babel/core@^7.0.0".
warning "@quasar/app > webpack > ajv-keywords@3.4.0" has incorrect peer dependency "ajv@^6.9.1".
warning " > eslint-loader@2.1.2" has unmet peer dependency "webpack@>=2.0.0 <5.0.0".
[5/5] Building fresh packages...
success Saved lockfile.
Done in 46.18s.

 [*] Running eslint --fix to comply with chosen preset rules...

yarn run v1.15.2
$ eslint --ext .js,.vue src --fix
Done in 1.92s.

 [*] Quasar Project initialization finished!

To get started:

  cd goodluck
  quasar dev

Documentation can be found at: https://v1.quasar-framework.org

Quasar is relying on donations to evolve. We'd be very grateful if you can
take a look at: https://www.patreon.com/quasarframework
Any amount is very welcomed.
If invoices are required, please first contact razvan@quasar-framework.org

Please give us a star on Github if you appreciate our work:
https://github.com/quasarframework/quasar

Enjoy! - Quasar Team
PS C:\Users\ealverr> cd .\goodluck\
PS C:\Users\ealverr\goodluck> quasar dev
 Error Unknown command "dev"

  ___
 / _ \ _   _  __ _ ___  __ _ _ __
| | | | | | |/ _` / __|/ _` | '__|
| |_| | |_| | (_| \__ \ (_| | |
 \__\_\\__,_|\__,_|___/\__,_|_|

  Example usage
    $ quasar <command> <options>

  Help for a command
    $ quasar <command> --help
    $ quasar <command> -h

  Options
    --version, -v Print Quasar CLI version

  Commands
    create        Create a project folder
    info          Display info about your machine
                    (and your App if in a project folder)
    upgrade       Check (and optionally) upgrade Quasar packages
                    from a Quasar project folder
    serve         Create an ad-hoc server on App's distributables
    help          Displays this message

  --------------
  => IMPORTANT !
  => Trigger this inside of a Quasar project for more commands.

What were you expecting?

I expect the command quasar dev to work as intended.

What steps did you take, to get the error?

Steps described above.

nothingismagick commented 5 years ago

I seem to remember a while back someone else had a similar problem because they were trying to install on windows in a similar path

averri commented 5 years ago

@nothingismagick, thanks for that, but it didn't work.

rstoenescu commented 5 years ago

There is definitely something wrong with your setup, because I got confirmation from multiple Windows 10 users (and also tested myself on a Win 10 in a VM) that it works correctly.

What does goodluck contain? Can you post the output of a dir command inside of it? Quasar seems to not recognize that newly created folder as a quasar project.

nothingismagick commented 5 years ago

This is currently in discussion right now in #v1-beta

averri commented 5 years ago

This is the contents of the goodluck dir:

 drwxr-xr-x 1 ealverr 1049089      0 Apr 24 23:08 src/                                                                                                                                                              
 -rw-r--r-- 1 ealverr 1049089   1348 Apr 24 23:08 .eslintrc.js                                                                                                                                                      
 -rw-r--r-- 1 ealverr 1049089     20 Apr 24 23:08 README.md                                                                                                                                                         
 -rw-r--r-- 1 ealverr 1049089   3598 Apr 24 23:08 quasar.conf.js                                                                                                                                                    
 -rw-r--r-- 1 ealverr 1049089     69 Apr 24 23:08 babel.config.js                                                                                                                                                   
 -rw-r--r-- 1 ealverr 1049089    815 Apr 24 23:08 .stylintrc                                                                                                                                                        
 -rw-r--r-- 1 ealverr 1049089    200 Apr 24 23:08 .postcssrc.js                                                                                                                                                     
 -rw-r--r-- 1 ealverr 1049089    258 Apr 24 23:08 .gitignore                                                                                                                                                        
 -rw-r--r-- 1 ealverr 1049089      6 Apr 24 23:08 .eslintignore                                                                                                                                                     
 -rw-r--r-- 1 ealverr 1049089    147 Apr 24 23:08 .editorconfig                                                                                                                                                     
 -rw-r--r-- 1 ealverr 1049089    901 Apr 24 23:08 package.json                                                                                                                                                       
 drwxr-xr-x 1 ealverr 1049089      0 Apr 24 23:09 node_modules/                                                                                                                                                     
 drwxr-xr-x 1 ealverr 1049089      0 Apr 24 23:09 ./                                                                                                                                                                
 -rw-r--r-- 1 ealverr 1049089 337264 Apr 24 23:09 yarn.lock                                                                                                                                                         
 drwxr-xr-x 1 ealverr 1049089      0 Apr 24 23:17 ../
VitalJeevanjot commented 5 years ago

=> Trigger this inside of a Quasar project for more commands. So far I just pointed out you are not in quasar project directory, Or what quasar-cli thinks. Can you share the package.json file?

smolinari commented 5 years ago

Are you running git bash as admin? On my Win 10 system, I had to make sure any programs I run for development need to be ran in admin mode.

Scott

VitalJeevanjot commented 5 years ago

@smolinari That's also a good point, But just to inform that am using quasar v1 and mostly use PowerShell without admin mode.

averri commented 5 years ago

Are you running git bash as admin? On my Win 10 system, I had to make sure any programs I run for development need to be ran in admin mode.

Scott

Yes, I have tested using admin mode and the same issue happens. Thanks for commenting.

averri commented 5 years ago

=> Trigger this inside of a Quasar project for more commands. So far I just pointed out you are not in quasar project directory, Or what quasar-cli thinks. Can you share the package.json file?

I'm sure I'm in a Quasar directory. The quasar-cli does not recognize it as is.

This is the contents of package.json:

{
  "name": "goodluck",
  "version": "0.0.1",
  "description": "A Quasar Framework app",
  "productName": "Quasar App",
  "cordovaId": "org.cordova.quasar.app",
  "author": "ealverr",
  "private": true,
  "scripts": {
    "lint": "eslint --ext .js,.vue src",
    "test": "echo \"No test specified\" && exit 0"
  },
  "dependencies": {
    "@quasar/extras": "^1.0.0",
    "quasar": "^1.0.0-beta.0"
  },
  "devDependencies": {
    "@quasar/app": "^1.0.0-beta.0",
    "@vue/eslint-config-standard": "^4.0.0",
    "babel-eslint": "^10.0.1",
    "eslint": "^5.10.0",
    "eslint-loader": "^2.1.1",
    "eslint-plugin-vue": "^5.0.0",
    "strip-ansi": "=3.0.1"
  },
  "engines": {
    "node": ">= 8.9.0",
    "npm": ">= 5.6.0",
    "yarn": ">= 1.6.0"
  },
  "browserslist": [
    "last 1 version, not dead, ie >= 11"
  ],
  "resolutions": {
    "ajv": "6.8.1"
  }
}
averri commented 5 years ago

I have tested Quasar v1-beta with Node 12 and it's working fine:

PS C:\Users\ealverr\projects\goodgod> quasar info
Operating System - Windows_NT(10.0.16299) - win32/x64
NodeJs - 12.0.0

Global packages
  NPM - 6.9.0
  yarn - 1.15.2
  @quasar/cli - 1.0.0-beta.4
  cordova - Not installed

Important local packages
  quasar - 1.0.0-beta.18 -- High performance, Material Design 2, full front end stack with Vue.js -- build SPA, SSR, PWA, Hybrid Mobile Apps and Electron apps, all simultaneously using the same codebase
  @quasar/app - 1.0.0-beta.19 -- Quasar Framework App CLI
  @quasar/extras - 1.1.1 -- Quasar Framework fonts, icons and animations
  vue - 2.6.10 -- Reactive, component-oriented view layer for modern web interfaces.
  vue-router - 3.0.6 -- Official router for Vue.js 2
  vuex - 3.1.0 -- state management for Vue.js
  electron - Not installed
  electron-packager - Not installed
  electron-builder - Not installed
  @babel/core - 7.3.4 -- Babel compiler core.
  webpack - 4.30.0 -- Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
  webpack-dev-server - 3.3.1 -- Serves a webpack app. Updates the browser on changes.
  workbox-webpack-plugin - 4.3.0 -- A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache.
  register-service-worker - 1.6.2 -- Script for registering service worker, with hooks

Quasar App Extensions
  *None installed*

Networking
  Host - IE-00000617
  vEthernet (DockerNAT) - 10.0.75.1
  Ethernet - 159.107.167.234
  vEthernet (Default Switch) - 172.17.44.209
  vEthernet (nat) - 172.28.240.1
PS C:\Users\ealverr\projects\goodgod> quasar dev
 Dev mode.......... spa
 Pkg quasar........ v1.0.0-beta.18
 Pkg @quasar/app... v1.0.0-beta.19
 Debugging......... enabled

 app:quasar-conf Reading quasar.conf.js +0ms
 app:dev Checking listening address availability (0.0.0.0:8080)... +5ms
 app:webpack Extending SPA Webpack config +541ms
 app:generator Generating Webpack entry point +17ms
 app:dev-server Booting up... +5ms

  SPA █████████████████████████ [100%] in ~6s

 DONE  Compiled successfully in 6239ms                                                                                                                                                                                             1:34:06 PM

 N  App dir........... C:\Users\ealverr\projects\goodgod
    App URL........... http://localhost:8080/
    Dev mode.......... spa
    Pkg quasar........ v1.0.0-beta.18
    Pkg @quasar/app... v1.0.0-beta.19

 app:dev-server Opening default browser at http://localhost:8080/ +6s
averri commented 5 years ago

Hi Razvan,

you're welcome. I can help with that, just let me know the best time for you. I'll be available from 10am to 5pm Irish time.

Em qui, 25 de abr de 2019 às 15:32, Razvan Stoenescu < notifications@github.com> escreveu:

@averri https://github.com/averri

Ok, thanks for answering and ruling out all of the obvious things. I'll prepare some changes in quasar/cli but can we sync together tomorrow (Friday) so we can do a teamviewer session to try some fixes directly on your machine pls? Would take 30-40 minutes of your time but I'd appreciate this very much. I can't reproduce on any Win 10 machine that I touched.

In my mind, the culprit is resolve-from underlying package which I will replace with my own code.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/quasarframework/quasar/issues/3965#issuecomment-486697515, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOPPT6I4Y5J4AT7DFWDTQLPSG6G7ANCNFSM4HIID67A .

rstoenescu commented 5 years ago

@averri please ping me on Discord. Preparing a bulletproof approach for quasar/cli and will need you to test it. Thanks for your time!

rstoenescu commented 5 years ago

Seems like didn't sync. @averri Can you install latest @quasar/cli (1.0.0-beta.5) and report if any errors? npm i -g @quasar/cli@latest. I've enhanced the way quasar/cli deferrs to local quasar/app.

Thanks.

averri commented 5 years ago

Hi @rstoenescu, I have tested the new @quasar/cli@1.0.0-beta.5 and it's working fine on Windows 10 with Nodejs 10.x. I even tested nvm, and now developers can easily switch Node versions and quasar/cli is working fine. Great!

averri commented 5 years ago

Hi Razvan,

are you online on Discord? I can't find you.

Yes, I'll try the latest quasar beta with Node 10.x (the one I was having issues).

Em sex, 26 de abr de 2019 às 17:02, Razvan Stoenescu < notifications@github.com> escreveu:

Seems like didn't sync. @averri https://github.com/averri Can you install latest @quasar/cli (1.0.0-beta.5) and report if any errors? npm i -g @quasar/cli@latest. I've enhanced the way quasar/cli deferrs to local quasar/app.

Thanks.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/quasarframework/quasar/issues/3965#issuecomment-487110607, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOPPTYCOBUWON23QMHVD43PSMRSBANCNFSM4HIID67A .

averri commented 5 years ago

Good news: the new version is working fine on my Windows 10, with Nodejs 10.x. I'm even using nvm, so I can easily switch Node versions. Nice!

Em sex, 26 de abr de 2019 às 20:02, Alexandre Verri < alexandreverri@gmail.com> escreveu:

Hi Razvan,

are you online on Discord? I can't find you.

Yes, I'll try the latest quasar beta with Node 10.x (the one I was having issues).

Em sex, 26 de abr de 2019 às 17:02, Razvan Stoenescu < notifications@github.com> escreveu:

Seems like didn't sync. @averri https://github.com/averri Can you install latest @quasar/cli (1.0.0-beta.5) and report if any errors? npm i -g @quasar/cli@latest. I've enhanced the way quasar/cli deferrs to local quasar/app.

Thanks.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/quasarframework/quasar/issues/3965#issuecomment-487110607, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOPPTYCOBUWON23QMHVD43PSMRSBANCNFSM4HIID67A .

rstoenescu commented 5 years ago

Thanks for reporting!

shakeelosmani commented 5 years ago

I am facing the same issue on windows 10, Did this on my mac and worked fine, however, I have the same issue like op on windows 10

@rstoenescu your help on this is truly appreciated.

Additional note: we have production apps built on other Node.JS frameworks and thus updating node version is not a possibility. It works fine in the same node version on Mac. But at work we are a windows shop and the CI tools are all built for windows.

windowsissuequasar

smolinari commented 5 years ago

@shakeelosmani - can you please take your issue to either either the forum or the discord channel?. You'll get answers there for sure. Please just have some patience.

Thanks. 😄

Scott

shakeelosmani commented 5 years ago

@smolinari thanks for the tip, Iasked the same question on the discord channel. Fingers crossed.

Arman-Ahmed-Jony commented 5 years ago

I am having exactly the same problem.

nothingismagick commented 5 years ago

Try removing node and reinstalling 10LTS @Arman-Ahmed-Jony

Arman-Ahmed-Jony commented 5 years ago

[solution]

step 1: run cmd/command line in the project folder npm install

step 2: quasar dev if errors like bellow comes [error] 1:23 error Expected linebreaks to be 'LF' but found 'CRLF' linebreak-style

use the following command npm run lint -- --fix

that's how i solved this problem. i hope this will help you

cashmisa commented 4 years ago

Had the same issue with node 8.9. (but not with 8.10.), found this thread and upgraded nodejs and problem solved.

Thanks for sharing

grb2015 commented 4 years ago

share my case .

I clone a repo from github. run quasar and the same error occor. In my case , I run npm install / or yarn install . finally ,everything goes well.

engbaher77 commented 4 years ago

i have same issue , Fixed with updating node version to v12.18.1

disarticulate commented 1 year ago

Just ran into this issue w/v2. Leaving this note for the google searches:

  quasar - 2.7.5 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
  @quasar/app - 3.3.3 -- Quasar Framework local CLI
  @quasar/extras - 1.15.0 -- Quasar Framework fonts, icons and animations

On windows, it looks like Quasar creates quasar.config.js and on Unix, it creates quasar.conf.js

I copied the windows app, freshly made, to unix and ran quasar dev and got the warning. I then created a new app to port over and when copying the files, found the name difference.

Maiconph commented 7 months ago

=> Trigger this inside of a Quasar project for more commands. So far I just pointed out you are not in quasar project directory, Or what quasar-cli thinks. Can you share the package.json file?

tnks guy i want a this respost ty