fix(next-plugin): build not outputting css on windows

[syfxlin]

Fix #1086 #929

Next.js removes the resource matching query (!=!) and the inline loader (!virtual-file-loader.js?{}!), so you need to pass the virtual CSS file directly to noop.css, and then extract the virtual CSS file from noop.css via a loader like this:

import "noop.css?{ filename, source }"

This PR change is validated for Windows/Linux/macOS and can be used to output CSS normally in Next.js 13 & React Server Components.

References:

• syfxlin/next-plugin-vanilla-extract
• syfxlin/vanilla-extract-demos

[changeset-bot]

🦋 Changeset detected

Latest commit: c3f3c82

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@vanilla-extract/next-plugin	Patch
@vanilla-extract/webpack-plugin	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[askoufis]

Thanks for the contribution! Fingers crossed this addresses all existing next.js issues.

I checked out your demos repo on windows and linux and can confirm that everything is working as expected. Also tested your next plugin with some of the reproductions in the next.js issues and they work too.

[hazzo]

Did not fixed this #1152. Had to rollback and apply the patch with patch-package :S

[askoufis]

Did not fixed this #1152. Had to rollback and apply the patch with patch-package :S

@hazzo The PR never stated that it would fix that issue. I was hopeful in the above comment that it might fix other issues, but it didn't. It seems that #1152 is caused by something else.