Add a workaround for a Yarn v1 bug

We cannot use `process-polyfill` as the package name due to a bug in Yarn v1. The errors results in a dependency conflict with `node-stdlib-browser` which fails to import `process/browser.js`.
yarnpkg/yarn#6907

Author: davidmyersdev

package.json

@@ -73,7 +73,7 @@
     "@rollup/plugin-inject": "^5.0.3",
     "buffer-polyfill": "npm:buffer@^6.0.3",
     "node-stdlib-browser": "^1.2.0",
-    "process-polyfill": "npm:process@^0.11.10"
+    "process": "^0.11.10"
   },
   "peerDependencies": {
     "vite": "^2.0.0 || ^3.0.0 || ^4.0.0"

pnpm-lock.yaml

@@ -1,5 +1,8 @@
 const global = globalThis || this || self
 
 export { Buffer } from 'buffer-polyfill'
-export { default as process } from 'process-polyfill'
+// We cannot use `process-polyfill` as the package name due to a bug in Yarn v1. The errors results in a dependency
+// conflict with `node-stdlib-browser` which fails to import `process/browser.js`.
+// https://github.com/yarnpkg/yarn/issues/6907
+export { default as process } from 'process'
 export { global }

shims/index.ts

@@ -133,10 +133,6 @@ export const nodePolyfills = (options: PolyfillOptions = {}): Plugin => {
     if (isDevEnabled(optionsResolved.globals.Buffer) && /^(?:node:)?buffer$/.test(name)) {
       return require.resolve('buffer-polyfill')
     }
-
-    if (isDevEnabled(optionsResolved.globals.process) && /^(?:node:)?process$/.test(name)) {
-      return require.resolve('process-polyfill')
-    }
   }
 
   return {