Jason Miller

Hi @Teajey! Currently Microbundle assumes a single dist/output directory, which means it's not possible to have a single `microbundle ...` command bundle both a parent directory and subpackage directories. However,...

Hiya - sorry for the slow reply. I'm glad you figured out the issue. Microbundle infers whether packages should be bundled or left as imports/requires based on your dependencies, and...

There are a few ways to do this. ### 1. Prefer HTML links Links are automatically intercepted and will invoke `route()` on any Router with a matching or default route....

@rejhgadellaa ah! sorry, I messed up the example for `#2` - it should be `contextType` (singular): ```js class C extends Component { static get contextType() { return LocationProvider.ctx; } render()...

@rejhgadellaa my suggestion here would be to move LocationProvider out of all of your components, and have one small root component that only renders the providers for your app: ```js...

I love this idea, but I do find myself wondering if that would be better served as a separate project?

What do you mean by dealing with it in the router? Something like a config for "add trailing slash"? (would have to be a regex to prevent it being appended...

~Hmm - this shouldn't be required, `mangle.json` should support "properties" as a top-level key. I don't believe it is nested under a `mangle` property, perhaps that's the issue?~ Ah, I...

The warning is only harmless if its a check for `this` from something like tslib. In other cases, it's a nontrivial change in behavior (and almost always a bug). One...

Heh - if you're running TS manually before passing things to Microbundle that would be a rollup use case. Any particular reason you'd need to do that though?