Unable to spin up the application due to StyleSheet import error

[rough bone]

Hey guys, I'm working on this application for the first time and after following these steps - https://github.com/nathanbowang/payload-concurrent-login-issue?tab=readme-ov-file#development

I'm unable to spin up the application. I've connected through Docker to connect locally and after doing pnpm dev it throws error

Error Message

Error evaluating Node.js code

Build Output

./packages/next/src/elements/DocumentHeader/Tabs/Tab/index.scss
Error evaluating Node.js code
Error: Can't find stylesheet to import.
╷
1 │ @import 'vars';
│ ^^^^^^
╵
packages\ui\src\scss\styles.scss 1:9 @import
packages\next\src\elements\DocumentHeader\Tabs\Tab\index.scss 1:9 root stylesheet
(from C:\Users\Tushar\payload\node_modules.pnpm\next@16.2.0_@opentelemetry+63122224f908b098e4aec8b12be3467a\node_modules\next\dist\build\webpack\loaders\resolve-url-loader\index.js, C:\Users\Tushar\payload\node_modules.pnpm\next@16.2.0@opentelemetry+_63122224f908b098e4aec8b12be3467a\node_modules\next\dist\compiled\sass-loader\cjs.js)
Caused by: Error: Can't find stylesheet to import.

Any help would be appreciated. Thanks!

[terse jetty]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Hooks Overview - Root Hooks - afterError
• Collection Hooks - Config Options - afterError
• Using Payload outside Next.js - Importing the Payload Config outside of Next.js - Troubleshooting
• Customizing CSS & SCSS - Global CSS
• Hooks Overview - Root Hooks

Community-Help:

• build /admin/styles.css

[somber gazelle]

Hey @rough bone is there a specific reason you're using that repo? From the name alone, it appears that is a repo specifically made as a reproduction to log an issue with Payload, so I would not use that as a base for a new project.

Instead I would use npx create-payload-app and pick one of our templates

[rough bone]

Hey @somber gazelle not using that repo as base, base repo is the original repo, I'm using the steps provided by that repo to spin up the application and reproduce the bug

[somber gazelle]

I guess I am a little confused then—is your goal to fix the bug?

[rough bone]

yes https://github.com/payloadcms/payload/issues/16027 I'm trying to fix this bug for which I followed the steps provided by Nathan in his repo (using Docker instead of spinning up local Mongo instance)

[somber gazelle]

It looks like someone else has already pulled a PR that addresses that issue!

https://github.com/payloadcms/payload/pull/16052

[rough bone]

Ohh just now it got added I guess wasn't there 15 mins back

Thanks for the help