Webpack: Fix for process fallback using require.resolve

[merceyz]

Issue: #16896

@storybook/builder-webpack5 uses the ProvidePlugin to provide a polyfill of the process module but doesn't resolve the absolute path to it nor declare it as a dependency.

There are more dependency issues but I'll leave those for another time.

What I did

Use require.resolve to get the absolute path to process/browser.js and declare process as a dependency.

How to test

• Is this testable with Jest or Chromatic screenshots?
• Does this need a new example in the kitchen sink apps?
• Does this need an update to the documentation?

The PnP e2e test should catch this but it seems it has other issues at the moment.

[nx-cloud]

☁️ Nx Cloud Report

CI ran the following commands for commit 1310bc3. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 1 target

• nx run-many --target=prepare --all --parallel --max-parallel=15

---

Sent with 💌 from NxCloud.

[shilman]

Thanks @merceyz !! 🙏 Added a fix for the manager-webpack5 dependency also