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

Getting error when starting with quasar for first time #46

Closed
aswinkp opened this Issue Oct 13, 2017 · 5 comments

Comments

Projects
None yet
2 participants
@aswinkp

aswinkp commented Oct 13, 2017

I just updated quasar-cli, and ran the three commands as mentioned in getting started section.

quasar init default app_name
cd app_name
npm install
quasar dev

localhost:8080 opens, but unfortunately, it says Cannot GET /

and console reads

error  in ./src/App.vue
Syntax Error: Unexpected token {
@ ./src/main.js 23:15-31
@ multi ./build/hot-reload.js ./src/main.js

I neither opened the editor nor edited any file. So this should be an issue from starter kit.

vue 2.3.4
quasar-framework 0.14.4

@rstoenescu

This comment has been minimized.

Show comment
Hide comment
@rstoenescu

rstoenescu Oct 13, 2017

Member

Hi,

Cannot reproduce this. What is your environment (OS and version, nodejs version, npm version, terminal, any other relevant tools that you use)?

Member

rstoenescu commented Oct 13, 2017

Hi,

Cannot reproduce this. What is your environment (OS and version, nodejs version, npm version, terminal, any other relevant tools that you use)?

@aswinkp

This comment has been minimized.

Show comment
Hide comment
@aswinkp

aswinkp Oct 13, 2017

@rstoenescu Ubuntu 16.04, npm 4.4.1, node 4.2.6

I just created another project with quasar init default#v0.13 app_name . It works without any issues.

But not working when started with 0.14 template

aswinkp commented Oct 13, 2017

@rstoenescu Ubuntu 16.04, npm 4.4.1, node 4.2.6

I just created another project with quasar init default#v0.13 app_name . It works without any issues.

But not working when started with 0.14 template

@rstoenescu

This comment has been minimized.

Show comment
Hide comment
@rstoenescu

rstoenescu Oct 13, 2017

Member

http://forum.quasar-framework.org/topic/972/solved-failed-to-compile-with-1-errors
Upgrade nodejs to at least v6 (latest LTS). For better performance I also recommend upgrading npm to its latest 5.x version.

Member

rstoenescu commented Oct 13, 2017

http://forum.quasar-framework.org/topic/972/solved-failed-to-compile-with-1-errors
Upgrade nodejs to at least v6 (latest LTS). For better performance I also recommend upgrading npm to its latest 5.x version.

@rstoenescu rstoenescu closed this Oct 13, 2017

@aswinkp

This comment has been minimized.

Show comment
Hide comment
@aswinkp

aswinkp Oct 13, 2017

@rstoenescu Thanks. That was totally unexpected. Atleast the error message should tell to update node version.

Maybe it would be great if the below lines were included in Getting Started docs.

node -v
//check if the version is greater than x.x.x

aswinkp commented Oct 13, 2017

@rstoenescu Thanks. That was totally unexpected. Atleast the error message should tell to update node version.

Maybe it would be great if the below lines were included in Getting Started docs.

node -v
//check if the version is greater than x.x.x
@rstoenescu

This comment has been minimized.

Show comment
Hide comment
@rstoenescu

rstoenescu Oct 13, 2017

Member

The v0.15 starter kit will auto-check if nodejs and npm versions are right. Thanks for reporting this!

Member

rstoenescu commented Oct 13, 2017

The v0.15 starter kit will auto-check if nodejs and npm versions are right. Thanks for reporting this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment