8b85801852
This ensures we remove null bytes from the resolved path as it isn't valid when using `path`/`fs`. Additional tests have been added to ensure this is handled properly. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Errors have helpful link attached, see `contributing.md` Fixes: https://github.com/vercel/next.js/issues/30298 |
||
---|---|---|
.. | ||
terser-webpack-plugin | ||
wellknown-errors-plugin | ||
build-manifest-plugin.ts | ||
copy-file-plugin.ts | ||
css-minimizer-plugin.ts | ||
font-stylesheet-gathering-plugin.ts | ||
jsconfig-paths-plugin.ts | ||
middleware-plugin.ts | ||
mini-css-extract-plugin.ts | ||
next-drop-client-page-plugin.ts | ||
next-trace-entrypoints-plugin.ts | ||
nextjs-require-cache-hot-reloader.ts | ||
nextjs-ssr-import.ts | ||
pages-manifest-plugin.ts | ||
profiling-plugin.ts | ||
react-loadable-plugin.ts | ||
serverless-plugin.ts | ||
telemetry-plugin.ts |