Why isn't quasar "build" a known command?

Question

I'm running quasar build in my bitbucket pipeline but the output is: Error Unknown command "build"

Anybody know why this happens? I basically want to just push my code and let bitbucket pipeline take care of the rest.

image: node:10.15.3

pipelines:
  branches:
      master:
        - step:
          name: Building Quasar
          caches:
              - node
          script:
              - yarn global add @quasar/cli
              - quasar build
              - do some other stuff
          artifacts:
              - path/to/artifact
    - step:
          name: Deploying to S3
          caches:
            - node
          script:
              - cp $BITBUCKET_CLONE_DIR/path/to/artifact path/to/artifact
              - pipe: atlassian/aws-s3-deploy:0.3.8
                variables:
                  ...

Answer 1

It's a common mistakes that occurred during getting packages with package manager. In default yarn package manager doesn't get dev dependencies if NODE_ENV set to production. You have 3 solutions:

1. move all packages from dev dependencies to dependencies(that is not rational).
2. Set NODE_ENV to development.
3. Run Yarn install --production=false when you want to get all dependencies.

Answer 2

from https://forum.quasar-framework.org/topic/5283/unknown-command-build-circleci/5

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

In my case fixed executing like this:

npm install && npm install --only=dev
npm install @quasar/cli
npx quasar build