No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. CLI
    Log in to post
    • Newest to Oldest
    • Oldest to Newest
    • Most Posts
    • Most Votes
    • J

      init quasar with specific version
      cli setup version • • janviehweger

      1
      0
      Votes
      1
      Posts
      1038
      Views

      No one has replied

    • A

      Error with " npm install "
      • asv

      4
      0
      Votes
      4
      Posts
      3961
      Views

      S

      @asv better to use yarn.

    • L

      quasar wrap cordova => App is already wrapped with cordova
      • livioweb

      4
      0
      Votes
      4
      Posts
      1672
      Views

      P

      I think you wrap the app only the first time.

    • LaurentPayot

      Introducing npx: an npm package runner
      • LaurentPayot

      2
      2
      Votes
      2
      Posts
      1227
      Views

      S

      Awesome, thanks for sharing !

    • rohityadav

      I have just started to v0.14.0 issue in compilation error
      • rohityadav

      3
      0
      Votes
      3
      Posts
      1239
      Views

      rohityadav

      @spectrolite , thanks fixed this issue as you suggested in this post (http://forum.quasar-framework.org/topic/522/upgrade-guide-for-0-14-beta)

    • P

      Expected Spaces Not Tabs
      • packy

      4
      0
      Votes
      4
      Posts
      1951
      Views

      a47ae

      As @rstoenescu said, just edit the .eslintrc.js file in your project to look like this:

      module.exports = { root: true, parser: 'babel-eslint', parserOptions: { sourceType: 'module' }, env: { browser: true, }, // https://github.com/feross/standard/blob/master/RULES.md#javascript-standard-style extends: 'standard', // required to lint *.vue files plugins: [ 'html' ], globals: { 'cordova': true, 'DEV': true, 'PROD': true, '__THEME': true }, // add your custom rules here 'rules': { // allow paren-less arrow functions 'arrow-parens': 0, 'one-var': 0, 'import/first': 0, // allow debugger during development 'no-debugger': process.env.NODE_ENV === 'production' ? 2 : 0, 'brace-style': [2, 'stroustrup', { 'allowSingleLine': true }], 'indent': ['error', 'tab'] // This is the required line to use tabs instead of spaces } }

      Please note, I copied the whole file, but the only line you need to add is 'indent': ['error', 'tab'] to the rules section.

    • S

      quasar project not run after build
      • Sujan Dev

      4
      0
      Votes
      4
      Posts
      1721
      Views

      rstoenescu

      @Sujan-Dev Upgrading the CLI shouldn’t break anything. The build process is defined by the starter kit that you are using (see /build folder in your project’s folder). You say that you build and then serve the dist folder from an apache server and it doesn’t works. If it worked before upgrading the CLI, it should work just the same after upgrading it. Nothing changed regarding build. The problem is elsewhere. I am a little confused as you then say “the project is run in dev mode”. Are you serving the distributable (/dist) or are you running the development server? In both situations, upgrading CLI won’t break anything. It may be your apache at fault. Have you tried with quasar serve command after making a build? It does an ad-hoc web server pointed to your distributable – so basically same thing as apache.

    • R

      fix uglifyjs problem
      • remy

      4
      0
      Votes
      4
      Posts
      2444
      Views

      R

      @LaurentPayot Great !
      Thank you 😁

    • K

      Issues
      • kourosz

      6
      0
      Votes
      6
      Posts
      2984
      Views

      s.molinari

      @kourosz - http://forum.quasar-framework.org/topic/248/quasar-cli-v0-5-1-works-with-proxies-too

      Scott

    • A

      Karma configuration required
      • alexe2baranov

      2
      0
      Votes
      2
      Posts
      1397
      Views

      s.molinari

      Here are some past threads, which might answer your question.

      http://forum.quasar-framework.org/topic/101/testing-in-version-0-9-1
      http://forum.quasar-framework.org/topic/175/testing

      Scott

    • C

      WARNING in asset size limit
      • cherry314159

      5
      0
      Votes
      5
      Posts
      3816
      Views

      Martin

      @cherry314159 it’s indeed a “bug” that sneeked into one of latest webpack builds. I fixed it in the base file.

      As for “bigness”, quasar is not big yet in terms of nr of contributors, but it is in terms of completeness. On top of that, it’s high quality code/ low bugs. At least that’s been my experience for last 3 months. Also gitstars are rising rapidly.

    • LaurentPayot

      NodeJS workflow
      • LaurentPayot

      6
      0
      Votes
      6
      Posts
      3600
      Views

      LaurentPayot

      I understand. No worries. Focusing on the front-end is a wise choice 👍