Is microbundle-crl still maintained?

[jruales]

The npm page for microbundle-crl points to this GitHub repo. I saw that microbundle has been regularly updated but the latest version of microbundle-crl is from 3 years ago. I'm also noticing that it depends on some old libraries that are triggering a Dependabot alert due to vulnerabilities in nth-check <2.0.1. Is microbundle-crl still being maintained? Or is it recommended to move to use microbundle instead? If so, is there some sort of guide for that transition?

[rschristian]

microbundle-crl can be found here. Indeed, the package meta data was never updated and it's been long unmaintained.

It's probably better to migrate to Microbundle proper, but there is a bit of a gap in behaviors supported by each. In general, microbundle is a JS bundler and tries to avoid supporting different asset types. There is some support, just less than microbundle-crl. A few flags will probably need to be set too, as microbundle defaults to Preact's JSX pragma rather than React's.

AFAIK there's no guide, as the author behind the fork never wrote one or officially archived the project.

[jruales]

Thanks @rschristian!

Also tagging @transitive-bullshit from microbundle-crl as FYI, since there's no way of adding GitHub Issues in that repo so I can't add it there

[rschristian]

FWIW, there is this thread: https://github.com/transitive-bullshit/create-react-library/issues/284

It's a few years old, so some of the advice might not be accurate anymore, but some people have contributed migration steps.

[transitive-bullshit]

Please don't use microbundle-crl. It was a fork of microbundle and is no longer maintained.

[jruales]

Thanks for the update @transitive-bullshit! Since it's no longer maintained, may I suggest, to avoid confusion of future users, that you:

• deprecate the npm package
• update the README so that it informs users to move to microbundle
• archive the GitHub repo, and
• point the npm page to the archived repo so that people see the README with those instructions when they click on the link, instead of being directed to the current repo without further instructions?

[rschristian]

I'm going to close this out, as there isn't anything actionable for this repo.

If you do try to migrate and get stuck, feel free to ask here or open a new issue and we can take a look and give advice. Thanks!

[Stan-Stani]

Advice for those who run into the issue of microbundle-crl not supporting TS template literal types like: ${number}: use yarn resolutions to force the typescript version higher.

"resolutions": {
    "typescript": "^5.3.3"
  },