# esbuild-node-builtins-sideeffects

**Repository Path**: mirrors_mjackson/esbuild-node-builtins-sideeffects

## Basic Information

- **Project Name**: esbuild-node-builtins-sideeffects
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2021-04-23
- **Last Updated**: 2026-05-31

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

This repo shows how esbuild leaves the `import` for unused node builtins in the output bundle.

To reproduce:

```
$ npm install
$ npm run build
```

Then inspect `output.js`.

Now switch the `import` in `input.js` to import from `./local-fs` instead of `fs`. Run the build again and you should not see the `import` in the output because there is a `sideEffects: false` in `package.json`.

It'd be nice if esbuild used an implicit `sideEffects: false` for node builtins since they are purely library code and don't have any side effects.