microbundle icon indicating copy to clipboard operation
microbundle copied to clipboard

📦 Zero-configuration bundler for tiny modules.

Results 114 microbundle issues
Sort by recently updated
recently updated
newest added

I was trying to figure out why my code was doing the wrong thing, and ran into the fact that using `--format=modern` still seems to yield legacy JS: ``` >...

This is a weird request and I could be confused but here it goes. So there are libraries like [BabylonJS ](https://www.babylonjs.com/)that are: - Large libraries. - Statically typed in typescript...

Feature Request

currently when running microbundle command, there is no indication as to what is happening and the progress of the process. The console just stays empty for 2-5 minutes and spits...

enhancement :rocket:
Feature Request

Hi there, Thank you for the great work you've done with microbundle. For the record, here is how I'm using the lib: `microbundle --jsx React.createElement --no-compress --format modern,cjs` I'm using...

question :grey_question:

I love the simplicity of microbundle, but I need to do a bit more than what the default configuration it builds up provides. More specifically, I want to be able...

increased scope

Plugin: https://www.npmjs.com/package/ttypescript The main benefit of this build plugin is the easy enabling of using TS "transformers" which are not a mainstream part of TypeScript core just yet. This includes...

needs more info
discussion
increased scope

Similar to Browserify+webworkify, or Rollup+[[rollup-plugin-bundle-worker]() or [rollup-plugin-webworkify](https://www.npmjs.com/package/rollup-plugin-webworkify)], is it possible to bundle a web worker's source along with microbundle output?

enhancement :rocket:

Currently I have a package `@namespace/package` built using microbundle. I want to store certain functionality in a subdirectory of the package e.g. `import { ... } from "@namespace/package/subdirectory"`. An example...

question :grey_question:
discussion
documentation

### Problem Microbundle hoists a `require()` call out of a `try {}` block in a dependency. When that `require()` call throws, it is not caught by the `try {}` block...

upstream