esbuild / esbuild.github.io Goto Github PK

Would you consider a PR to make this website one single page?

Similar to https://mpv.io/manual/master/ or https://rollupjs.org/guide/en/

pro:

• can ctrl-f to find anything (oh this is so so nice)

con:

• larger download, slower page

I made this electron+esbuild template. It'd be nice to mention it in the website.

https://github.com/dragonDScript/electron-esbuild-template

The link in the esbuild documentation about minification is outdated. Although it shows esbuild better than other minifiers, like swc, today's situation has changed and the picture that is shows is different. You might want to change https://github.com/privatenumber/minification-benchmarks/tree/cd3e5acb8d38da5f86426d44ac95974812559683#readme to just https://github.com/privatenumber/minification-benchmarks#readme or to a newer commit.

The Bundle Size Analyzer references an example-metafile.json which is not included in the repository, and as far as I can tell neither npm run build nor make -C src/analyze generate it.

How does the file get included in the gh-pages build, and how can I generate it myself?

Update docs on watch: { onRebuild } callback that may be implemented alternatively vi Plugins api as explained here: evanw/esbuild#1409 (comment)

• evanw/esbuild#1409

I'm trying to bundle a cli application with esbuild that uses esbuild internally to dynamically load modules. Now when i deno run the bundle the cli prints

Usage:
  esbuild [options] [entry points]

Documentation:
  https://esbuild.github.io/

Repository:
  https://github.com/evanw/esbuild
....

Which seems to be the same as when running esbuild itself in cli mode, could there be a scoping problem when bundling files with esbuild that themself consume esbuild as a library? Not however that bundling the same file with deno bundle or running the unbundled file with deno run executes my cli and works as expected.

As added last month.

If LICENSE allows, I'd like to use some source code in this repo, especially https://github.com/esbuild/esbuild.github.io/tree/main/src/analyze

Hi @evanw. Are you open to a pull request that documents how to implement a minimally viable rapid development / live-reload server? I’d be happy to submit a PR that explains the following:

1. Implement a minimal file watcher using a simple poll-based strategy (Go)
2. How to incrementally recompile esbuild based on file changes
3. How to use SSE (server-sent events) so the client browser tabs reload themselves when incremental recompilation is done

Your serve implementation helped me understand why a) native file watching can be a bad idea and b) how to strategically use HTTP servers to delay requests to prevent race conditions, etc., but it didn’t demonstrate to me how to make esbuild respond to filesystem changes and trigger reloads on client browser tabs.

I’d like to help document implementing this kind of dev server architecture from scratch in a few paragraphs with Go code examples.

No worries if you’d rather not, I just thought I’d try to help where I can be usefuk.

Relevant links:

• Implementing platform-independent, poll-based file watching in Go

  If you’re like me and want the simplest form-factor that you can actually understand / debug yourself, you can roll your own naive watcher in Go in <50 LOC:

  • Code: evanw/esbuild#21 (comment)

• MVP dev server: evanw/esbuild#645 (comment)

  So I figured out how to implement esbuild incremental recompilation + server-sent events to trigger reloads which feels like HMR but works today. I used this playground to validate my ideas: https://github.com/zaydek/esbuild-dev-server.

  • Playground: https://github.com/zaydek/esbuild-dev-server

I‘d like’to do the part of translation into Chinese

It would be useful to have a guide explaining how to migrate from Webpack 4/5 to esbuild. In particular an example taking a real Webpack config file and building the code with esbuild would be useful:

• Migrating from webpack.IgnorePlugins
• Migrating from webpack.DefinePlugin (setting process.env.FOO = someValue)
• How to migrate code using base64-inline-loader
• Migrating alias
• Migrating noParse clauses
• What to do with currently used additional loaders (like ng-annotate-loader)
• Migrating from webpack.HtmlWebpackPlugin
• Migrating from webpack.FaviconsWebpackPlugin
• Migrating from webpack.BannerPlugin