fix(webpack-plugin): 'require is not defined' error in Node 24

[Pnlvfx]

The webpack plugin was failing when used with Storybook in Node.js 24 environments due to ESM module resolution. Node.js attempts to execute the code as ESM where 'require' is not defined (reference: storybookjs/storybook#31434).

Edit:

⚠️ CJS Breakage with import.meta Workaround

If someone is experiencing this issue they can use my fork for now.

fix-esm-require

While this PR attempts to fix the ESM require issue in Node 24/ Storybook via createRequire(import.meta.url), it will break CJS environments where import.meta is undefined.

Leaving this open for discussion—please weigh in on tradeoffs.

[changeset-bot]

🦋 Changeset detected

Latest commit: aa28386

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/webpack-plugin	Patch
@vanilla-extract/next-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]

@Pnlvfx Thanks for the PR. I think this is the right fix, though there's a few more usages of require.resolve within the webpack and next.js plugins that need addressing. Preconstruct replaces import.meta.url in the CJS bundle with its own shim, so it still works.

I'll push a few more changes to your branch and get this PR merged and released as some of our internal tools are blocked by this bug.

[Pnlvfx]

@Pnlvfx Thanks for the PR. I think this is the right fix, though there's a few more usages of require.resolve within the webpack and next.js plugins that need addressing. Preconstruct replaces import.meta.url in the CJS bundle with its own shim, so it still works.

I'll push a few more changes to your branch and get this PR merged and released as some of our internal tools are blocked by this bug.

Great, thank you. i'm happy to have contributed to this ❤️