Ryan Christian

Sorry, `push-manifest` you could want, `manifest.json` is what I was referring to with that last comment. They're for PWAs, but seeing as how you've disabled the rest of the PWA...

There's no hard requirement, though it'd be quite odd.

Seems both service workers (esm and legacy) are having regenerator inserted in. I imagine they should be excluded?

Sorry for the late response, you can just use a custom template to get this behavior I believe. Copy [the template](https://github.com/preactjs/preact-cli/blob/master/packages/cli/lib/resources/template.html) if you do not already have one in your...

CSS inlining should still be there, that's something unrelated. There's some way to regex with the script src, though I forget exactly how. Regardless, Preact-CLI is mainly for PWAs. You're...

@jmoore34 That's the _CRA_ equivalent, which is just Webpack. You can configure Preact-CLI's Webpack config as-is, see [preact-cli#webpack](https://github.com/preactjs/preact-cli#webpack). That big Safari nomodule polyfill is gone now, and anything remaining you...

To expound a bit: most args don't have any type validation and rely upon fallbacks or (sometimes) questionable coercion deep into the tool. Warnings aren't raised to the user on...

Changes that I've thought of, maybe should be considered: - [x] Switching to automatic JSX runtime - Seems to be the way the community is going these days - Not...

Sounds reasonable. Feel free to submit a PR or something, otherwise I'll take a look when I get a block of time. I think I'll want to check over the...

Yeah `@storybook/preact` ends up dragging in `"html-webpack-plugin": "^4.0.0"` which is going to cause issues as we're a bit behind the Webpack releases here. I wouldn't recommend installing `[email protected]` over the...