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

    Unknown command "build" CircleCI

    Help
    3
    5
    2929
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      gradlon last edited by

      Hey Guys,
      I have the following issue.
      When I try to build the Quasar spa on circleCI i get an Unknown command “build”.

      The config looks like this.

        build-prod:
         machine: true
         steps:
           - checkout
           # start proprietary DB using private Docker image
           # with credentials stored in the UI
           - run:
               name: Install  Node.js 10.15.3 with build in nvm tool
               # https://www.cloudesire.com/how-to-upgrade-node-on-circleci-machine-executor/
               command: |
                 set +e
                 curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.5/install.sh | bash
                 export NVM_DIR="/opt/circleci/.nvm"
                 [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
                 nvm install v10.15.3
                 nvm alias default v10.15.3
      
                 # Each step uses the same `$BASH_ENV`, so need to modify it
                 echo 'export NVM_DIR="/opt/circleci/.nvm"' >> $BASH_ENV
                 echo "[ -s \"$NVM_DIR/nvm.sh\" ] && . \"$NVM_DIR/nvm.sh\"" >> $BASH_ENV
           - run: npm install -g @quasar/cli
           - run: quasar build
      

      Does anyone know how to get this working?
      Kind regards
      Gradlon

      1 Reply Last reply Reply Quote 0
      • s.molinari
        s.molinari last edited by s.molinari

        You (the user) need(s) to be in the project folder for the build command to work. Not that is the problem, but it might be.

        Scott

        1 Reply Last reply Reply Quote -1
        • G
          gradlon last edited by

          Hey,
          I found the Problem.
          For anyone running into this problem, the issue is that the dev dependencies are not installed, the fix was easy, I modified the config as follows.

          • run: npm install && npm install --only=dev

          After this, it works like a charm.

          Kind regards
          Gradlon

          1 Reply Last reply Reply Quote 1
          • s.molinari
            s.molinari last edited by

            Ah. Yes. Of course. The dependencies are needed for anything to work.

            Scott

            1 Reply Last reply Reply Quote 0
            • A
              aislan last edited by

              For me it’s happening the same problem.
              “yarn install” doesn’t fix it to me.

              quasar/cli installed is “1.1.2”

              1 Reply Last reply Reply Quote 0
              • First post
                Last post