Ryan Christian

Sorry, are you asking how to enforce integers as that path segment for the component as in differentiating `/api/v2/5` and `/api/v2/foo`, or asking how make the prop within the component...

Well, types not lining up doesn't mean it's incompatible necessarily. Ideally they would, but TS type incompatibilities are pretty common in the ecosystem as a whole. Now, if you get...

I believe this is intentional, use `import { Link } from 'preact-router/match';` instead when you want this behavior. [Implemented here](https://github.com/preactjs/preact-router/blob/c6915eb4431a36e2c365b6b0ffae1db833e53415/match/src/index.js#L13-L30) [Docs showing `preact-router/match` here](https://github.com/preactjs/preact-router#active-matching--links)

That's what inlining is, taking the CSS from the external stylesheet and add it into the HTML doc (usually to avoid FOUC). It sounds like you're asking about converting the...

No solution beyond running Babel separately and before this plugin, no. _I think_ that's fine and correct for my use case though, so it's not a problem.

Sorry, this isn't a simple use case. I have added this for `preact-cli`, which is a Webpack-based build tool. It's got a fair bit going on in it, but the...

No problem. Preact-CLI always have a need for `babel-loader`, as a) we need something to handle the dev environment and b) we need to handle JSX, TS, decorators, and any...

Gotcha, good to confirm; I didn't imagine the intent was to run this first to handle those transforms (assuming the babel config was customizable) but the docs pointed that way.

Should this be occurring in props too? For example, ```jsx render(h('div', { class: 'flex(& col)' })); // Results in ``` which is rather unexpected. Edit: Seems React does it too....

Under the "Integrating Into an Existing Pipeline", [the first item does go over how to configure Babel to work with Preact](https://preactjs.com/guide/v10/getting-started#setting-up-jsx). Seems like you might've skipped right over setting up...