activeClassName not supported in 3.0.0 with esModuleInterop: true

[patrickhulce]

activeClassName gets passed through to the a element as a regular attribute and is not used in the matching-style that is documented in the README.

It seems to be because the Link component defined in match.js is not actually exported. Instead the regular a passthrough component is exported.

preact-router/src/index.js

Lines 251 to 253 in 3eb5b31

	const Link = (props) => (
	createElement('a', assign({ onClick: handleLinkClick }, props))
	);

[patrickhulce]

For additional info, it seems like this might be an artifact of too smart commonjs compat which uses the Link defined on Router instead of the export {..., Link}.

I'm using parcel + typescript with esModuleInterop: true.

[developit]

@patrickhulce hmm - are you importing Link from preact-router/match? I just merged a PR to correct the docs, which were erroneously stating that { Link } from 'preact-router' supports activeClassName (it does not).

import { Link } from 'preact-router';
<Link activeClassName="foo" />  // does not work

import { Link } from 'preact-router/match';
<Link activeClassName="foo" />  // works

[patrickhulce]

I was indeed importing from root according to the previous docs.

Why is import { Link } from 'preact-router' not the link with matching behavior?

[developit]

It's a way to reduce the size of the core library. I think it may be worth evaluating what the size impact would be to merge <Match> and <Link activeClassName> into preact-router core. Only a percentage of folks use them, but they aren't very large.