Skip to content

node-fallbacks

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History
 
 

node-fallbacks

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
vendor
vendor
 
 
.gitignore
.gitignore
 
 
README.md
README.md
 
 
assert.js
assert.js
 
 
buffer.js
buffer.js
 
 
build-fallbacks.ts
build-fallbacks.ts
 
 
bun.lock
bun.lock
 
 
console.js
console.js
 
 
constants.js
constants.js
 
 
crypto.js
crypto.js
 
 
domain.js
domain.js
 
 
events.js
events.js
 
 
http.js
http.js
 
 
https.js
https.js
 
 
net.js
net.js
 
 
os.js
os.js
 
 
package.json
package.json
 
 
path.js
path.js
 
 
process.js
process.js
 
 
punycode.js
punycode.js
 
 
querystring.js
querystring.js
 
 
stream.js
stream.js
 
 
string_decoder.js
string_decoder.js
 
 
sys.js
sys.js
 
 
timers.js
timers.js
 
 
timers.promises.js
timers.promises.js
 
 
tsconfig.json
tsconfig.json
 
 
tty.js
tty.js
 
 
url.js
url.js
 
 
util.js
util.js
 
 
zlib.js
zlib.js
 
 

README.md

Browser polyfills for bun build --target=browser

When using bun build --target=browser, if you attempt to import a Node.js module, Bun will load a polyfill for that module in an attempt to let your code still work even though it's not running in Node.js or a server.

For example, if you import zlib, the node-fallbacks/zlib.js file will be loaded.

Not used by Bun's runtime

These files are not used by Bun's runtime. They are only used for the bun build --target=browser command.

If you're interested in contributing to Bun's Node.js compatibility, please see the src/js directory.