Can't find stylesheet to import

[stag-enterprises]

On a fresh install & build of Quartz, running the build task fails with

 Quartz v4.4.0

✘ [ERROR] Error: Can't find stylesheet to import.
  ╷
1 │ @use "variables.scss" as *;
  │ ^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
  ../../../../quartz/styles/base.scss 1:1  @use
  - 1:1                                    root stylesheet [plugin sass-plugin]

    quartz/plugins/emitters/componentResources.ts:8:19:
      8 │ import styles from "../../styles/custom.scss"
        ╵                    ~~~~~~~~~~~~~~~~~~~~~~~~~~

Couldn't parse Quartz configuration: ./quartz/build.ts
Reason: Error: Build failed with 1 error:
quartz/plugins/emitters/componentResources.ts:8:19: ERROR: [plugin: sass-plugin] Error: Can't find stylesheet to import.
  ╷
1 │ @use "variables.scss" as *;
  │ ^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
  ../../../../quartz/styles/base.scss 1:1  @use
  - 1:1                                    root stylesheet
error: script "quartz" exited with code 1

Compiling quartz/styles/custom.scss manually using npx sass works fine, so I'm pretty sure it's an issue with esbuilds-sass-plugin.

[aarnphm]

I'm confused how did you run into this issue?

If you do npm i and npx quartz build --serve without any modification, it should just work?

[stag-enterprises]

Weird, it doesn't seem to be working for me. I didn't make any changes to the repo, just cloning it and npx quartz build

[saberzero1]

Weird, it doesn't seem to be working for me. I didn't make any changes to the repo, just cloning it and npx quartz build

Is there a quartz/styles/variables.scss file in your repo?

Are there pending changes? git status

[stag-enterprises]

Is there a quartz/styles/variables.scss file in your repo?

Yes

Are there pending changes? git status

Just the default template files in content

[saberzero1]

Is there a quartz/styles/variables.scss file in your repo?

Yes

Are there pending changes? git status

Just the default template files in content

Can you try to do a clean install?

npm ci.

If building doesn't work after that, can you provide the output of these commands?

• node --version (Gets Node.js version)
• npm --version (Gets Node package manager version)
• npm list --depth=0 (Gets installed NPM packages with versions (without full dependency graph))

[Carnia]

Is there a quartz/styles/variables.scss file in your repo?

Yes

Are there pending changes? git status

Just the default template files in content

Can you try to do a clean install?

npm ci.

If building doesn't work after that, can you provide the output of these commands?

• node --version (Gets Node.js version)
• npm --version (Gets Node package manager version)
• npm list --depth=0 (Gets installed NPM packages with versions (without full dependency graph))

I used pnpm (node22, npm10), and this issue also occurred. After switching to npm, it returned to normal. Can you support pnpm?

[aarnphm]

imo if you want to switch to pnpm then you have to also update the package.json for the script itself.

This decision I will refer back to Jacky's decision. I don't have strong opinion/fluent enough in the JS ecosystem to have opinion on supporting multiple tools.

fwiw this can also be applied everywhere (even in Python ecosystem), where the decision of the repo should just to follow one tool for build system (in this case, npm is the most battle tested, albeit there are faster option out there, including bun or deno).

Upgrading to a different build tool requires changes to the core, which I don't think we have bandwidth atm. So if you want to propose a faster build tool, then by all means I'm all ear, as long as Jacky agrees with it.

tbh I don't find any problem with npm at all.