Didn't get a result from child compiler error occurs when dynamic routes params like /blogs/[blog-id]

[Katsukiniwa]

Describe the bug

After upgrade @vanilla-extract/next-plugin from 2.3.5 to v2.3.6, Didn't get a result from child compiler error occurs when dynamic routes params like /blogs/[blog-id], but /blogs/[id] don't occur error.

This is minimum reproduce repository
https://github.com/Katsukiniwa/nextjs-vanilla-extract-css-playground

reproduce step is

1. clone the above repository
2. run npm install
3. run npm run dev
4. access to http://localhost:3000/blogs/1

Reproduction

https://github.com/Katsukiniwa/nextjs-vanilla-extract-css-playground/actions/runs/7880973075/job/21503841452

System Info

System:
    OS: macOS 14.3.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 327.86 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.0 - ~/.volta/tools/image/node/20.11.0/bin/node
    npm: 10.2.5 - ~/.volta/tools/image/npm/10.2.5/bin/npm
    pnpm: 8.14.3 - ~/.volta/bin/pnpm
  Browsers:
    Chrome: 121.0.6167.160
    Safari: 17.3.1
  npmPackages:
    @vanilla-extract/css: ^1.14.1 => 1.14.1 
    @vanilla-extract/next-plugin: ^2.3.6 => 2.3.6

Used Package Manager

npm

Logs

➜ npn run dev

> nextjs-vanilla-extract-css-playground@0.1.0 dev
> next dev

   ▲ Next.js 14.1.0
   - Local:        http://localhost:3000

 ✓ Ready in 2.7s
 ○ Compiling /blogs/[blog-id] ...
 ⨯ ./src/app/blogs/[blog-id]/page.css.ts
Error: Didn't get a result from child compiler
Import trace for requested module:
./src/app/blogs/[blog-id]/page.css.ts
 ⨯ ./src/app/blogs/[blog-id]/page.css.ts

Validations

• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[mrm007]

Hi @Katsukiniwa, thanks for reporting this.

It sounds like it's related to the latest fix we did for the Webpack plugin in #1247.

[Katsukiniwa]

@mrm007
Thanks!
However, I do not understand the modified PR that you taught me due to my lack of technical skills, and it appears difficult to resolve this issue on my own.
Is it possible for one of the maintainers to handle this issue?

[mrm007]

@Katsukiniwa sorry, I didn't mean to say the solution is in the linked PR. Just a note to self and for @askoufis, who recently worked on that part of the codebase.