quasarframework / quasar-cli Goto Github PK

See http://forum.quasar-framework.org/topic/246

Scott

Software version

OS: Linux
Node: v4.2.6
NPM: 4.3.0
Any other software related to your bug:

$ quasar --version
0.5.2

What did you get as the error?

$ quasar dev


> [email protected] dev /home/noumir/quasar/new
> node build/script.dev.js

 Starting dev server with "mat" theme...
 Will listen at http://localhost:8080
 Browser will open when build is ready.

Build completed in 29.681s


ERROR  Failed to compile with 3 errors                                                                                                                       7:38:58 PM

 error  in ./src/App.vue

Syntax Error: Unexpected token {


 @ ./~/vue-style-loader!./~/css-loader?sourceMap!./~/vue-loader/lib/style-compiler?{"id":"data-v-029e8249","scoped":false,"hasInlineConfig":true}!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/App.vue 4:14-271 13:3-17:5 14:22-279
 @ ./src/App.vue
 @ ./src/main.js
 @ multi ./build/hot-reload ./src/main.js

 error  in ./src/components/Index.vue

Syntax Error: Unexpected token {


 @ ./~/vue-style-loader!./~/css-loader?sourceMap!./~/vue-loader/lib/style-compiler?{"id":"data-v-f21a033e","scoped":false,"hasInlineConfig":true}!./~/stylus-loader?sourceMap!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/components/Index.vue 4:14-334 13:3-17:5 14:22-342
 @ ./src/components/Index.vue
 @ ./src/components async ^\.\/.*\.vue$
 @ ./src/router.js
 @ ./src/main.js
 @ multi ./build/hot-reload ./src/main.js

 error  in ./src/components/Error404.vue

Syntax Error: Unexpected token {


 @ ./~/vue-style-loader!./~/css-loader?sourceMap!./~/vue-loader/lib/style-compiler?{"id":"data-v-4425fd1e","scoped":false,"hasInlineConfig":true}!./~/stylus-loader?sourceMap!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/components/Error404.vue 4:14-337 13:3-17:5 14:22-345
 @ ./src/components/Error404.vue
 @ ./src/components async ^\.\/.*\.vue$
 @ ./src/router.js
 @ ./src/main.js
 @ multi ./build/hot-reload ./src/main.js

What were you expecting?

No error with quasar dev

What steps did you take, to get the error?

Follow the getting started procedure:

$ quasar init new
$ cd new
$ npm install
$ quasar dev

Additional info

2 weeks ago, the command was working. The only differences between the 2 generated project is a few different versions in the dependencies:

$ npm outdated
Package                 Current  Wanted  Latest  Location
babel-eslint              7.1.1   7.2.0   7.2.0  quasar-app
css-loader               0.26.4  0.26.4  0.27.3  quasar-app
eslint                   3.17.1  3.18.0  3.18.0  quasar-app
eslint-config-standard    6.2.1   6.2.1   7.1.0  quasar-app
moment                   2.17.1  2.18.0  2.18.0  quasar-app
stylus-loader             2.5.1   2.5.1   3.0.1  quasar-app
vue-loader               11.1.4  11.2.0  11.2.0  quasar-app

By forcing those versions into the "new" package.json, the problem disappears.
I'm very much a noob in npm/webpack/..., so I'm not able to go further in my investigation. :(

Maybe someone will have an idea ?
Thanks!

By default, ESLint expects ECMAScript 5 syntax. You can override that setting to enable support for other ECMAScript versions …

(ESLint docs)

Should Quasar configure ESLint for ECMAScript 6, 7 or 8? This would be done by adding an ecmaVersion key to .eslintrc.js, for ex:

  parserOptions: {
    sourceType: 'module',
    ecmaVersion: 6
  },

OTOH, I don't know if this is working properly: I added this to handle template literals, but still keep getting errors for them.

I just went through the quickstart guide.

Updated NPM/node
installed quasar-cli
Installed the deps
Ran "quasar dev" in root (worked fine)
Ran "quasar wrap electron"
"npm install" in electron dir
Tried to run "quasar dev" in electron dir..
It throws this message and results in the npm log below.

Not really sure where to start debugging?
Hopefully someone has seen this before or have an idea as to why i'm unable to start the app. 😜

Error Message

[email protected] dev /Users/#username#/Sites/Tools/#AppName#/electron
cross-env NODE_ENV=development node_modules/electron/dist/electron electron.js
events.js:160
throw er; // Unhandled 'error' event
^

Error: spawn node_modules/electron/dist/electron ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
at Module.runMain (module.js:607:11)
at run (bootstrap_node.js:420:7)
at startup (bootstrap_node.js:139:9)
at bootstrap_node.js:535:3

npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/Cellar/node/7.4.0/bin/node" "/usr/local/bin/npm" "run" "dev"
npm ERR! node v7.4.0
npm ERR! npm v4.0.5
npm ERR! code ELIFECYCLE
npm ERR! [email protected] dev: cross-env NODE_ENV=development node_modules/electron/dist/electron electron.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] dev script 'cross-env NODE_ENV=development node_modules/electron/dist/electron > electron.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the quasar-electron-app package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! cross-env NODE_ENV=development node_modules/electron/dist/electron electron.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs quasar-electron-app
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls quasar-electron-app
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /Users/#username#/Sites/Tools/#AppName#/electron/npm-debug.log
Content of npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/Cellar/node/7.4.0/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'owner',
1 verbose cli 'ls',
1 verbose cli 'quasar-electron-app' ]
2 info using [email protected]
3 info using [email protected]
4 silly mapToRegistry name quasar-electron-app
5 silly mapToRegistry using default registry
6 silly mapToRegistry registry https://registry.npmjs.org/
7 silly mapToRegistry data Result {
7 silly mapToRegistry raw: 'quasar-electron-app',
7 silly mapToRegistry scope: null,
7 silly mapToRegistry escapedName: 'quasar-electron-app',
7 silly mapToRegistry name: 'quasar-electron-app',
7 silly mapToRegistry rawSpec: '',
7 silly mapToRegistry spec: 'latest',
7 silly mapToRegistry type: 'tag' }
8 silly mapToRegistry uri https://registry.npmjs.org/quasar-electron-app
9 verbose request uri https://registry.npmjs.org/quasar-electron-app
10 verbose request no auth needed
11 info attempt registry request try #1 at 9:09:56 PM
12 verbose request id 56aecadd36f39874
13 http request GET https://registry.npmjs.org/quasar-electron-app
14 http 404 https://registry.npmjs.org/quasar-electron-app
15 verbose headers { 'content-type': 'application/json',
15 verbose headers 'cache-control': 'max-age=0',
15 verbose headers 'content-length': '2',
15 verbose headers 'accept-ranges': 'bytes',
15 verbose headers date: 'Wed, 25 Jan 2017 20:09:57 GMT',
15 verbose headers via: '1.1 varnish',
15 verbose headers age: '0',
15 verbose headers connection: 'keep-alive',
15 verbose headers 'x-served-by': 'cache-bma7021-BMA',
15 verbose headers 'x-cache': 'MISS',
15 verbose headers 'x-cache-hits': '0',
15 verbose headers 'x-timer': 'S1485374996.616600,VS0,VE464',
15 verbose headers vary: 'Accept-Encoding' }
16 silly get cb [ 404,
16 silly get { 'content-type': 'application/json',
16 silly get 'cache-control': 'max-age=0',
16 silly get 'content-length': '2',
16 silly get 'accept-ranges': 'bytes',
16 silly get date: 'Wed, 25 Jan 2017 20:09:57 GMT',
16 silly get via: '1.1 varnish',
16 silly get age: '0',
16 silly get connection: 'keep-alive',
16 silly get 'x-served-by': 'cache-bma7021-BMA',
16 silly get 'x-cache': 'MISS',
16 silly get 'x-cache-hits': '0',
16 silly get 'x-timer': 'S1485374996.616600,VS0,VE464',
16 silly get vary: 'Accept-Encoding' } ]
17 error owner ls Couldn't get owner data quasar-electron-app
18 verbose stack Error: Registry returned 404 for GET on https://registry.npmjs.org/quasar-electron-app
18 verbose stack at makeError (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:302:12)
18 verbose stack at CachingRegistryClient. (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/> request.js:280:14)
18 verbose stack at Request._callback (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:210:14)
18 verbose stack at Request.self.callback (/usr/local/lib/node_modules/npm/node_modules/request/request.js:186:22)
18 verbose stack at emitTwo (events.js:106:13)
18 verbose stack at Request.emit (events.js:191:7)
18 verbose stack at Request. (/usr/local/lib/node_modules/npm/node_modules/request/request.js:1081:10)
18 verbose stack at emitOne (events.js:96:13)
18 verbose stack at Request.emit (events.js:188:7)
18 verbose stack at IncomingMessage. (/usr/local/lib/node_modules/npm/node_modules/request/request.js:1001:12)
19 verbose statusCode 404
20 verbose pkgid quasar-electron-app
21 verbose cwd /Users/#username#/Sites/Tools/#AppName#/electron
22 error Darwin 15.6.0
23 error argv "/usr/local/Cellar/node/7.4.0/bin/node" "/usr/local/bin/npm" "owner" "ls" "quasar-electron-app"
24 error node v7.4.0
25 error npm v4.0.5
26 error code E404
27 error 404 Registry returned 404 for GET on https://registry.npmjs.org/quasar-electron-app
28 error 404
29 error 404 'quasar-electron-app' is not in the npm registry.
30 error 404 You should bug the author to publish it (or use the name yourself!)
31 error 404 Note that you can also install from a
32 error 404 tarball, folder, http url, or git url.
33 verbose exit [ 1, true ]

i would like a CLI switch to specify a name option for components i create from templates.
maybe like this:

Usage: quasar-new <template> <name including subfolder if any>

Options:

  -h, --help  output usage information
  -l, --list  List available templates
  -n, --name  Include a name option in the generated .vue file

Templates are stored in /templates

Example:

  # get your available Component templates
  $ quasar new -l
  $ quasar new --list

  # generate .vue file from a Component template
  $ quasar new component Hello

# generate .vue file from a Component template with a name property
$ quasar new -n component Hello

  # generate .vue file from a template to a subfolder
  $ quasar new layout layout/about/help/Hello
  # the above creates src/components/layout/about/help/Hello.vue

and script tag generated would be:

<script>
export default {
  name: 'hello',
  data () {
    return {}
  }
}
</script>

Here is the current documentation of the analize property on the section about configuring quasar.conf build section:

Looking at the actual webpack code we can see that this is not completely accurate:

    if (cfg.build.analyze) {
      const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin
      webpackConfig.plugins.push(
        new BundleAnalyzerPlugin(Object.assign({}, cfg.build.analyze))
      )
    }

It is even better ! You can provide an object that will be used as options for BundleAnalyzerPlugin. This is a very handy feature that deserves more attention.

I also noted that this only happens on production mode, which is not documented neither.
By the way, is there any way to check mode while extending the webpack config from quasar config ? Can I just check the cfg.ctx.dev on the extendWebpack function ?

Regards

Accidentally upgraded my quasar-cli to the latest version, i want to restore to the previous version.

Hi,

manifest.js file doesn't have a hash in the file name, every time after I build and release the new version, the browser is still loading the older version of manifest.js, the users have to force reload or clear the browser cache to load the site correctly.
Then since the older chunk js might have been deleted while the development, the site will break, showing errors like this:

Error: Loading chunk 0 failed.
r — manifest.js:1:564

I think the solution should be adding hash for manifest.js file too.

Any idea?

Thanks a lot.

Hi @rstoenescu

Thanks for the great tool.

I am currently using quasar framework to create a custom template but I encountered an issue when using a private repository. I noticed that you've used download-git-repo library and in the options section, we can use clone: true to be able to download the template from private repositories.

I would like a support for passing options to quasar init command to be able to use git clone for downloading a custom template.

I can submit a PR to add the option.

Software version

OS: Mac
Node:
NPM:
Any other software related to your bug:

What did you get as the error?

SyntaxError: Use of reserved word 'export' in file quasar.esm.js

What were you expecting?

I'm using quasar-cli to create the webpack1&Vue2, when i finished installing all requires, it shows me the error.

What steps did you take, to get the error?

Software version

OS: Arch Linux
Node: 9.7.1
NPM: 5.7.1
Any other software related to your bug:

What did you get as the error?

$ quasar new page Profile Posts
 ✖ Template "page.vue" does not exists.

What were you expecting?

 app:new Generated page: src/pages/Profile.vue +0ms
 app:new Make sure to reference it in src/router/routes.js + 2ms

What steps did you take, to get the error?

In my app dir that I created. quasar dev works fine, everything else ok too.

On Windows 10, 64 bit, node 7.7.4, npm 3.10.8.

C:\Users\jvukovich.npmrc contents:
registry=http://registry.npmjs.org/
strict-ssl=false
ca=

Confirmed settings with: npm config ls -l

Executed: quasar init default#beta [folder]

Result: Failed to download App template @quasarframework/quasar-template-default#beta: RequestError: unable to get local issuer certificate

We are behind a Websense proxy and they have an in-between certificate installed to decrypt SSL traffic.

I found this: #17

So, my .npmrc is setup properly, and settings inspection reflects them.

Anything else I am missing / ideas?

Getting

(unknown) [Vue warn]: Error when rendering root instance: warn
:8080/#/:2961 Uncaught ReferenceError: _h is not defined(…)

after

quasar init default mywebsite
cd mywebsite
yarn
quasar dev

quasar-cli 0.4.1
yarn 0.17.10
Ubuntu 16.04

Referencing quasarframework/quasar#346

OS: Win 10
Node: 8.9
NPM: 5.5.1
Any other software related to your bug:
Quasar-Cli 0.15.7

What did you get as the error?

Unexpected behavior when calling quasar init without project name parameter.

Quasar inits project "undefined" in folder "undefined"

What were you expecting?

Init Quasar project in current folder, choose name in interactive cli

Software version

OS: win 10 64b
Node: v8.9.4
NPM: 5.6.0
Any other software related to your bug:
quasar --version
0.15.5

What did you get as the error?

On older project ("quasar-framework": "^0.14.4"), quasar dev does nothing. Process uses 10-12% of CPU, nothing happens, no console output.

But npm run dev runs smoothly

gulp-util is deprecated.

The warning suggests to replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5.

quasar dev works without errors but when trying to build I get this error

$ quasar build


> [email protected] build /home/jperelli/proteccionista-app
> node build/script.build.js

 WARNING!
 Do NOT use VueRouter's "history" mode if
 building for Cordova or Electron.

 Cleaned build artifacts.

 Building Quasar App with "mat" theme...

Build completed in 21.284s

Hash: df0b9ec307d771baac81
Version: webpack 2.2.1
Time: 21297ms
                                   Asset       Size  Chunks                    Chunk Names
            js/1.9171683b74816e9258f9.js    4.46 kB    1, 6  [emitted]         
fonts/MaterialIcons-Regular.012cf6a.woff    57.6 kB          [emitted]         
         fonts/Roboto-Light.37fbbba.woff    89.2 kB          [emitted]         
        fonts/Roboto-Medium.303ded6.woff    89.7 kB          [emitted]         
       fonts/Roboto-Regular.081b11e.woff    89.4 kB          [emitted]         
          fonts/Roboto-Thin.90d3804.woff    87.8 kB          [emitted]         
            js/0.436f2707e612d6e94430.js    5.06 kB    0, 6  [emitted]         
          fonts/Roboto-Bold.ad140ff.woff    89.2 kB          [emitted]         
            js/2.59c775d07c221c49f610.js    1.73 kB    2, 6  [emitted]         
            js/3.79d66cbac0c98d41bdec.js     2.7 kB    3, 6  [emitted]         
                            js/vendor.js    1.13 MB    4, 6  [emitted]  [big]  vendor
                               js/app.js    7.01 kB    5, 6  [emitted]         app
                          js/manifest.js    1.53 kB       6  [emitted]         manifest
app.3392693b69c210d69d3bacae149a4702.css     253 kB    5, 6  [emitted]  [big]  app
                              index.html  634 bytes          [emitted]         

ERROR in js/vendor.js from UglifyJs
SyntaxError: Name expected [js/vendor.js:37083,23]

 Build complete with "mat" theme in "/dist" folder.

 Built files are meant to be served over an HTTP server.
 Opening index.html over file:// won't work.

I noticed a minor typo when adding a mode to my project:

app:mode-electron Electron support was addedd

I want to avoid install quasar-cli to global because I avoid execute any quasar command anywhere.

I want to command below.
bash:

$ mkdir myapp
$ cd myapp
$ npm install quasar-cli
$ $(npm bin)/quasaer init .

powershell:

$ mkdir myapp
$ cd myapp
$ npm install quasar-cli
$ &"$(npm bin)\quasaer.cmd" init .

I wrote this patch, but I don't have any MacOS device, so I can not test it.
https://github.com/nak1114/quasar-cli

Background: I have been using Quasar-Cli to build PWAs and hybrid Mobile apps. Recently, Vue-cli update has been released as v3.0.0-beta.1. It has a new command, "vue create my-project" which allows manual selection of features . One feature that I particularly found interesting is usage of Typescript in .vue/SFCs.

Feature Request: Allow Typescript in Quasar-starter-kit.

It would be cool to have a CLI command, which would allow users of Quasar to get a screen printout of valuable troubleshooting info such as OS, Node, NPM and Quasar versions. Users could cut and paste this info into their bug reports.

The command could be something like quasar info.

I'll be glad to take on this work. During the coming week I'll put up a PR.

Any further improvements to this idea would be greatly appreciated.

Scott

Referencing quasarframework/electron-wrapper/issues/7

Software version

OS:
Node:
NPM:
Any other software related to your bug:

What did you get as the error?

What were you expecting?

What steps did you take, to get the error?

I cannot run 'quasar wrap' command on Windows even though I've installed cordova globally

C:\Users\kamilersz\quasar\proj>quasar wrap
 i Generating Cordova wrapper for Quasar App...
{ [Error: spawn cordova ENOENT]
  code: 'ENOENT',
  errno: 'ENOENT',
  syscall: 'spawn cordova',
  path: 'cordova',
  spawnargs: [ 'create', 'wrapper' ] }
 x You need Cordova globally installed (npm install -g cordova).

C:\Users\kamilersz\quasar\proj>cordova -v
6.2.0

C:\Users\kamilersz\quasar\proj>npm -v
3.6.0

C:\Users\kamilersz\quasar\proj>node -v
v5.7.0

Referencing quasarframework/quasar#234 (comment)

Hi, I try install quasar on windows machine, when execute command 'npm install' i got error for installing 'babel-preset-es2015' package,
According what https://babeljs.io/ told i replaced 'babel-preset-es2015' to 'babel-preset-env' and problem solved,
but later when i executed command 'quasar dev' got error:
Module build failed: Error: Couldn't find preset "es2015" relative to directory.
Is there any plan to upgrade from 'babel-preset-es2015' to 'babel-preset-env' ?
Someone has any solution for this issue?

During development I noticed that 'vueRouterMode: hash' was causing the formatting of the url to be localhost:'portnumber'/index.html#/.

This lead me to set my htmlFilename to and empty string.

When I went to build my app I received and error due to setting this to an empty string. After discussing this issue with @rstoenescu he pointed out that I needed to remove that. I brought up the issue about the formatting URL issue, and it was noted that this was how vue-router handled the routing, but after I went back to my old quasar app, as well as looking at the basic Vue app using vue-router in hash mode, the format was still: localhost:'portnumber'/#/

I went and tested my hypothesis and edited the second half of the ternary operator to '#/' and removed the 'cfg.build.htmlFilename', so: localhost:'portnumber'/#/

So I did some digging in the cli and noticed at line 350 in quasar-config.js:

cfg.build.APP_URL = `http${cfg.devServer.https ? 's' : ''}://${host}:${cfg.devServer.port}/${cfg.build.vueRouterMode === 'hash' ? cfg.build.htmlFilename : ''}`

With that I did a quick experiment, and changed the file to:

cfg.build.APP_URL = `http${cfg.devServer.https ? 's' : ''}://${host}:${cfg.devServer.port}/${cfg.build.vueRouterMode === 'hash' ? '#/' : ''}`

Dev worked as I hoped, as did the build. Tested on http-server and the same format worked.

Can I make a minor request for a future release, or will this cause bigger issues that I'm not aware of?

Thanks!

Hello !

To integrate Quasar in a client/server structure, I moved quasar root folder into a sub-folder "client" and reconfigured packages.json and webpack paths to have quasar work from its new location.

Problem : when using quasar new command and after had a look on this repository, quasar-new assume there is an src folder from the root of the project which is no longer the case in the current structure I'm using now.

I think the simpler way to correct this should be to be able to give the new location of the /src folder (and templates/ inside it) using a parameter from this command, like :

quasar new --list --base-path=/client/src or
quasar new component Hello --base-path=/client/src

Is it something possible to have ? Or wants me to PR ?

Thanks anyway.

how to configure multi font format, there's only one font format now. some browsers can't recognize woff font, this cause showing text instead of icon

Currently, when creating a shared volume between the host and the docker container, the CLI fails, because the CLI says the same directory, where we want to initialize with the CLI, already exists. It does fail correctly, because of the shared volume.

What we want is for the CLI to to see if the directory is empty or not. If the directory is empty, then the initialization will be allowed.

Scott

Hi,

First, congratulations for all the work done in Quasar these last weeks ! Happy to see the community growing day after day.

Just switched to Babun (a Windows terminal that uses Cygwin) and I can't run quasar dev from Babun.
When running quasar dev in my project folder, I have the following error :

'npm' is not recognized as an internal or external command,
operable program or batch file.

My PATH env var is OK and I can run the npmcommand without problem :

{ my-app } develop » npm                          /cygdrive/l/disque/workspace/my-app
Usage: npm <command>

where <command> is one of:
    access, adduser, bin, bugs, c, cache, completion, config,
    ddp, dedupe, deprecate, dist-tag, docs, edit, explore, get,
    help, help-search, i, init, install, install-test, it, link,
    list, ln, logout, ls, outdated, owner, pack, ping, prefix,
    prune, publish, rb, rebuild, repo, restart, root, run,
    run-script, s, se, search, set, shrinkwrap, star, stars,
    start, stop, t, tag, team, test, tst, un, uninstall,
    unpublish, unstar, up, update, v, version, view, whoami

npm <cmd> -h     quick help on <cmd>
npm -l           display full usage info
npm help <term>  search for help on <term>
npm help npm     involved overview

Specify configs in the ini-formatted file:
    C:\Users\mika\.npmrc
or on the command line via: npm <command> --key value
Config info can be viewed via: npm help config

[email protected] L:\disque\outils\nodejs\node_modules\npm

My PATH variable is exported in the .babunrc file :

...

# NodeJS
export NODEJS_HOME=/cygdrive/l/disque/outils/nodejs

# NPM
export NPM_HOME=/cygdrive/l/disque/outils/npm

# Path
export PATH=${NODEJS_HOME}:${NPM_HOME}:${PATH}

Child processes launched with the spawn function in node normally inherit from the parent env vars, right ? I can't understand why this child process doesn't know the npm command.

Referencing quasarframework/quasar#1680

I don't see it in any milestone or existing issue yet, so I figured I'd put it on your radar. It's supposed to be a lot faster 60 - 98% faster, in fact.

Just as the title says.

By the way, cannot avoid to thank everybody involved in quasar-framework for such a great work.

I install quasar-cli globaly but when i want to use commands termux throw this error:

usr/lib/node_modules/quasar-cli/bin/quasar-list(1) does not exist, try --help

/data/data/com.termux/files/usr/lib/node_modules/quasar-cli/bin/quasar-init(1) does not exist, try --help

/data/data/com.termux/files/usr/lib/node_modules/quasar-cli/bin/quasar-list(1) does not exist, try --help

But its bullshit that file exist!
I found similar issues on vue-cli but not any fix was there.

Tnx

Quasar: 0.6.4
OS: android 6 and 7 with termux
Node:6.11.2
NPM:3.10.10

Hi Guys,
Thanks for the greate work tha you made !
I think that autogenerated main.js is not always a good idea because sometimes we need to make business logic in.

Software version

OS: Ubuntu 17.10
Node: v4.7.2
NPM: 3.5.2
Any other software related to your bug:

What did you get as the error?

Exit Code 0

What were you expecting?

Exit Code 1? Really just anything other than 0

What steps did you take, to get the error?

Import an unused componenet, then run quasar build. Despite ✘ 1 problem (1 error, 0 warnings), it exits with 0. I'm trying to integrate quasar build with Travis CI, so it would be helpful if quasar build did not exit with 0 when it encounters problems.

It would be greatly useful (for bug reporting as well as other uses) if quasar version also showed the currently installed versions of at least npm and Vue, and maybe a few other key packages, like quasar-extras or webpack.

> quasar version -v
Quasar CLI v0.6.2
webpack  v2.2.1
npm v2.15.11
  
  App running on Quasar v0.14.0 (edge version)
  quasar-extras  v0.0.7
  vue  v2.3.4

Just a suggestion. What do you guys think ?

Running Ubuntu ARM on Chromebook in chroot environment;

installed npm (v2.15.9) and nodejs (v4.5.0)

installed quasar through npm

sudo npm install -g quasar-cli

when running quasar init i get following error

 ℹ Generating Quasar App...

⠧ Determining newest template.../usr/local/lib/node_modules/quasar-cli/lib/template-list.js:18
      JSON.parse(branches).filter(function (branch) {
                           ^

TypeError: JSON.parse(...).filter is not a function
    at Request._callback (/usr/local/lib/node_modules/quasar-cli/lib/template-list.js:18:28)
    at Request.self.callback (/usr/local/lib/node_modules/quasar-cli/node_modules/request/request.js:187:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)
    at Request.<anonymous> (/usr/local/lib/node_modules/quasar-cli/node_modules/request/request.js:1044:10)
    at emitOne (events.js:77:13)
    at Request.emit (events.js:169:7)
    at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/quasar-cli/node_modules/request/request.js:965:12)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)

   ╭───────────────────────────────────────╮
   │                                                                                                    │
   │    Update available 0.2.0 → 0.4.1                                               │
   │   Run npm i -g quasar-cli to update                                            │
   │                                                                                                    │
   ╰───────────────────────────────────────╯

Running npm i -g quasar-cli to update does not solve the problem;

after upgrading postcss-loader from 1.3.3 to 2.x, quasar dev reports errors like https://github.com/postcss/postcss-loader/issues/209 (in both 0.13 and 0.14beta)

According to the link above, postcss-loader v2 no longer uses LoaderOptionsPlugin in the webpack config file, so the webpack configuration needs to be fixed if we are to upgrade to postcss-loader v2

Currently quasar-cli already provides a well known electron-packager integration to bundle Electron-based applications in an executable format. I wonder if this project could get a step further and integrate electron-builder/electron-forge as well, providing so a complete solution for packaging apps in a distributable format (Windows installer, macOS dmg, Linux DEB/RPM/AppImage/Snap/Flatpak, etc.).

Both projects provide an API so they could be integrated into quasar-cli. Note, however, that both support different targets:

• electron-builder supports:
  • all platforms: 7z, zip, tar.xz, tar.7z, tar.lz, tar.gz, tar.bz2)
  • macOS: dmg, pkg, mas (macOS)
  • Linux: AppImage, snap, deb, rpm
  • Windows: nsis (Installer), nsis-web (Web installer), portable (portable app without installation), AppX (Windows Store), MSI, Squirrel.Windows
• electron-forge supports:
  • all platforms: zip
  • macOS: dmg
  • Linux: flatpak, deb, rpm (AppImage and snap available via electron-builder plugin)
  • Windows: AppX, Squirrel.Windows (nsis and nsis-web available via electron-builder plugin)

Quasar-cli that was released a few hours ago is version 0.15.6. In package.json, I saw that it is dependent on version 0.15.5 of quasar-framework. How about updating that too to version 0.15.6 of quasar-framework?

Software version

OS:
Node:
NPM:
Any other software related to your bug:

What did you get as the error?

What were you expecting?

What steps did you take, to get the error?

Software version

OS: OSX 10.12.6
Node: 8.4.0
NPM: 5.4.0
Any other software related to your bug:

What did you get as the error?

internal/child_process.js:325
throw errnoException(err, 'spawn');
^

Error: spawn EACCES
at _errnoException (util.js:1041:11)
at ChildProcess.spawn (internal/child_process.js:325:11)
at exports.spawn (child_process.js:493:9)
at Command.executeSubCommand (/usr/local/lib/node_modules/quasar-cli/node_modules/commander/index.js:546:14)
at Command.parse (/usr/local/lib/node_modules/quasar-cli/node_modules/commander/index.js:471:17)
at Object. (/usr/local/lib/node_modules/quasar-cli/bin/quasar:41:4)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)

What were you expecting?

No error

What steps did you take, to get the error?

Running either quasar version or quasar init testproj causes the error. Brand new install of what should be v14.2.

The problem looks like it's caused by incorrect file permissions (none executable) in /usr/local/lib/node_modules/quasar-cli/bin, so the spawn command fails on these:

-rw-r--r--    506B Oct 25  2016 quasar-build
-rw-r--r--     60B Oct 25  2016 quasar-clean
-rw-r--r--    2.8K Mar  1 10:00 quasar-dev
-rw-r--r--    2.5K Mar 31 05:08 quasar-init
-rw-r--r--     59B Oct 25  2016 quasar-lint
-rw-r--r--    937B Aug 18 08:04 quasar-list
-rw-r--r--    2.3K Nov  1  2016 quasar-new
-rw-r--r--    1.1K Apr  4 12:55 quasar-serve
-rw-r--r--    654B Oct 25  2016 quasar-test
-rw-r--r--    1.0K Mar 31 05:08 quasar-version
-rw-r--r--    1.3K Nov 15  2016 quasar-wrap

quasar-serve fails silently when no folder is specified with latest PR #30.

It looks like commander never executes the action function.

Hi,
would be nice to have a template with best practices, featuring:

• login/signup page
• router with several pages (taking into account if the user has logged in)
• pages containing several components
• api calls (auth, get, post, put, delete) for REST
• internationalisation, auto-detect language
• optional: a graphql client
• optional: switch theme from white to black
  Thank you

Software version

OS: archlinux
Node: 9.4
NPM: yarn 1.3.2
Any other software related to your bug:

What were you expecting?

It works.

What steps did you take, to get the error?

start a new quasar project in a repository managed by yarn workspace.

What did you get as the error?

These dependencies were not found:

* ansi-html in /home/ctaf/src/lana/node_modules/quasar-cli/node_modules/webpack-dev-server/client/overlay.js
* /home/ctaf/src/lana/packages/lana-pwa/.quasar/entry.js in multi /home/ctaf/src/lana/node_modules/quasar-cli/node_modules/webpack-dev-server/client?http://localhost:8080 webpack/hot/dev-server ./.quasar/entry.js
* html-entities in /home/ctaf/src/lana/node_modules/quasar-cli/node_modules/webpack-dev-server/client/overlay.js
* loglevel in /home/ctaf/src/lana/node_modules/quasar-cli/node_modules/webpack-dev-server/client?http://localhost:8080
* sockjs-client/dist/sockjs in /home/ctaf/src/lana/node_modules/quasar-cli/node_modules/webpack-dev-server/client/socket.js
* strip-ansi in /home/ctaf/src/lana/node_modules/quasar-cli/node_modules/webpack-dev-server/client?http://localhost:8080
* webpack/hot in /home/ctaf/src/lana/node_modules/quasar-cli/node_modules/webpack-dev-server/client?http://localhost:8080
* webpack/hot/dev-server in multi /home/ctaf/src/lana/node_modules/quasar-cli/node_modules/webpack-dev-server/client?http://localhost:8080 webpack/hot/dev-server ./.quasar/entry.js
* webpack/hot/emitter in /home/ctaf/src/lana/node_modules/quasar-cli/node_modules/webpack-dev-server/client?http://localhost:8080

To install them, you can run: npm install --save ansi-html /home/ctaf/src/lana/packages/lana-pwa/.quasar/entry.js html-entities loglevel sockjs-client/dist/sockjs strip-ansi webpack/hot webpack/hot/dev-server webpack/hot/emitter

Temporary fix:

run ln -sf <root_repository>/node_modules packages/<myquasar_app>

Feel free to tell me how to debug / help.

For CoffeeScript I use the following /quasar.conf.js > build > extendWebpack(cfg).

      extendWebpack (cfg) {
        cfg.resolve.extensions.push('.coffee')
        // first rule is for Vue single file components
        cfg.module.rules[0].options.loaders.coffee = ['babel-loader', 'coffee-loader']
        cfg.module.rules.push({
          test: /\.coffee$/,
          loaders: ['babel-loader', 'coffee-loader'],
          include: [__dirname + '/src']
        })
      }

There is a trick with Vuex because the presence of store/index.js is hardcoded in https://github.com/quasarframework/quasar-cli/blob/dev/lib/quasar-config.js
so you can't use store/index.coffee. A quick workaround is to use the following store/index.js:

import store from './index.coffee'
export default store