Modular Dashboard Sass issue

[rubixvi]

Describe the Bug

./nodemodules/.pnpm/@payloadcms+ui@3.69.0@type_f6dae4b1d169b9370a166162f9bf6e5f/node_modules/@payloadcms/ui/dist/widgets/CollectionCards/index.scss

Error evaluating Node.js code
Error: Can't find stylesheet to import.
  ╷
1 │ @import 'vars';
  │         ^^^^^^

Causes admin to crash, this is likely related to development on any Windows.

Link to the code that reproduces this issue

NA

Reproduction Steps

Fresh install latest on any windows device and boot up to admin.

Which area(s) are affected?

area: templates

Environment Info

PS F:\rubix-main-payload\rubix-payload> pnpm payload info

Binaries:
  Node: 22.21.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  payload: 3.69.0
  next: 16.1.0
  @payloadcms/db-mongodb: 3.69.0
  @payloadcms/graphql: 3.69.0
  @payloadcms/live-preview: 3.69.0
  @payloadcms/live-preview-react: 3.69.0
  @payloadcms/next/utilities: 3.69.0
  @payloadcms/plugin-cloud-storage: 3.69.0
  @payloadcms/plugin-redirects: 3.69.0
  @payloadcms/plugin-seo: 3.69.0
  @payloadcms/plugin-stripe: 3.69.0
  @payloadcms/richtext-lexical: 3.69.0
  @payloadcms/storage-s3: 3.69.0
  @payloadcms/translations: 3.69.0
  @payloadcms/ui/shared: 3.69.0
  react: 19.2.3
  react-dom: 19.2.3
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 65438
  Available CPU cores: 16

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload

[Dan6erbond]

Same here, and it looks like we're both using PNPM so unsure if it's related:

Error evaluating Node.js code
Error: Can't find stylesheet to import.
  ╷
1 │ @import 'vars';
  │         ^^^^^^
  ╵
  node_modules\.pnpm\@payloadcms+ui@3.69.0_@type_b48077cfac2efb2ea07413081d6e4a06\node_modules\@payloadcms\ui\dist\scss\styles.scss 1:9                    @import
  node_modules\.pnpm\@payloadcms+ui@3.69.0_@type_b48077cfac2efb2ea07413081d6e4a06\node_modules\@payloadcms\ui\dist\widgets\CollectionCards\index.scss 1:9  root stylesheet
Caused by: Error: Can't find stylesheet to import.
  ╷
1 │ @import 'vars';
  │         ^^^^^^

[amirHizkiya]

Same. Downgrading fixed the issue as well.

[rubixvi]

@paulpopus i think this needs to be looked at....

However, I feel like it's related to this: vercel/next.js#87243

Problem is, running in webpack still produces the issue.

[rubixvi]

Temporary work around

pnpm patch @payloadcms/ui

open up nodes_modules
.pnpm_patches/@payloadcms/ui@3.69.0/dist/widgets/CollectionCards/index.scss

Change line 1 to @import '../../scss/styles';
instead of the ~ symlink

run the pnpm patch-commit that you received from the console previously.

should now all boot up fine, remember to remove the patch-package and the entry once a release to fix this has been done.