Comments (5)
I was able to determine that the process
shim is what causes the dev tools to not work. My best guess is that the plugin relies on overriding process
itself in dev. I need to think through how I want the interface to work, but I'll likely expose a way to disable the shims for process
, global
, and Buffer
for either dev or build.
from vite-plugin-node-polyfills.
This has been fixed in v0.9.0
. For your specific issue, you'll want to do something like this.
import { defineConfig } from 'vite'
import { nodePolyfills } from 'vite-plugin-node-polyfills'
export default defineConfig({
plugins: [
nodePolyfills({
globals: {
process: 'build',
},
}),
],
})
from vite-plugin-node-polyfills.
I'll have to dig into this more, but I'm thinking the react
plugin must be injecting something into the browser that is relying on a certain API to not be polyfilled.
from vite-plugin-node-polyfills.
Having the same issue here, would love to help out if possible.
from vite-plugin-node-polyfills.
Here is another repro not using the react plugin and excluding every option possible. It is still not working: https://codesandbox.io/p/sandbox/optimistic-panini-95xb2d
from vite-plugin-node-polyfills.
Related Issues (20)
- Missing "./shims/global" specifier HOT 4
- TypeError: net.createConnection is not a function HOT 7
- When vite define contains process.env: xx, process polyfill will fail HOT 1
- Migrate to `unenv`
- Release `v1.0.0`
- Cannot find module 'vite-plugin-node-polyfills/shims/buffer' HOT 9
- Missing kMaxLength and SlowBuffer exposure HOT 1
- toString error with zlib starting with 0.18.0 HOT 2
- Failed to resolve module specifier "vite-plugin-node-polyfills/shims/global". Relative references must start with either "/", "./", or "../". HOT 3
- Failed to resolve import "vite-plugin-node-polyfills/shims/buffer" HOT 6
- Error when having type: module in package.json HOT 1
- `process` is not polyfilled if `viteConfig.define` is used to define, for example, a static environment variable in the form of `process.env.var_name` HOT 2
- Cannot access "fs/promises.readFile" in client code.
- bug: config `include: [],` treated as `no option is passed`
- Globals are always defined HOT 1
- Bug: conflict with another middleware plugin HOT 3
- Bug: PassThrough is not exported by "__vite-browser-external" during build
- Bug: exports is not defined HOT 2
- Bug: importing 'crypto' polyfill leads to error `exports is not defined` with yarn build && yarn preview in nuxt HOT 2
- Bug: `node:assert/strict` is not polyfilled
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vite-plugin-node-polyfills.