fix: Allow React 19 as peer dependency

[Sidnioulz]

• Port to React 18/19 syntax
• Add Storybook 9 to peer dependencies
• Port local package to Storybook 9
• Update CI runners and jobs
• Audit and update all tooling
• Replace jest with vitest
• Replace webpack with vite
• Enable auto with labels
• Migrate package to type=module

@xyc it'd be lovely if you could please disable your Netlify app on this repo. It's giving out errors and we can't disable it from our side. Thanks!

📦 Published PR as canary version: 7.0.1--canary.190.17416995031.0

✨ Test out this PR locally via:

npm install react-inspector@7.0.1--canary.190.17416995031.0
# or 
yarn add react-inspector@7.0.1--canary.190.17416995031.0

[netlify]

✅ Deploy Preview for sb-react-inspector ready!

Name	Link
🔨 Latest commit	260b804
🔍 Latest deploy log	https://app.netlify.com/projects/sb-react-inspector/deploys/68a59109f3132c0008aca1ca
😎 Deploy Preview	https://deploy-preview-190--sb-react-inspector.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Sidnioulz]

Still needing a NPM_TOKEN secret to produce the canary.

[xyc]

@Sidnioulz It should be disabled now.

[Sidnioulz]

@Sidnioulz It should be disabled now.

Thank you!

[ndelangen]

@JReinhold have we setup auto correctly?

I suspect if merged, the release version won't be bumped correctly, can you check/confirm/ give advice please?

[ndelangen]

@Sidnioulz I think the upgrades are all concluded, and the npm publishing is confirmed to work.

[Sidnioulz]

@JReinhold have we setup auto correctly?

I suspect if merged, the release version won't be bumped correctly, can you check/confirm/ give advice please?

IIRC auto bumps versions based on PR labels only. If the job runs from a PR hook, it should bump. But if it doesn't, we should get a NPM publish conflict version anyway.

[Sidnioulz]

Thanks so much for finishing this tidy up @ndelangen!

[Sidnioulz]

@ndelangen alas, the release job got skipped: https://github.com/storybookjs/react-inspector/actions/runs/17417753185/job/49449864005.

We made it release on main (source). But this repo is so old it's still on master. I don't have privileges to switch default branches so I'm gonna have to delegate that to you.

I also notice Dependabot is paused, also lacking privs to resume it.

Once the NPM release is done, I can take care of cleaning up all the stale issues and communicating to the Remix router people.

[ndelangen]

Looks like changing the default branch did cause a release to happen, but pushing the git tags failed.

https://www.npmjs.com/package/react-inspector?activeTab=versions

[Sidnioulz]

I see 8.0 though!

https://www.npmjs.com/package/react-inspector/v/8.0.0

[ndelangen]

Yeah, it seemed to have skipped 7.0.0 completely.

I suspect I've setup auto incorrectly. @JReinhold can you please tell me if that's the case?

[Sidnioulz]

Yeah, it seemed to have skipped 7.0.0 completely.

I suspect I've setup auto incorrectly. @JReinhold can you please tell me if that's the case?

That was my fault. Kinda the reason why I'm not too comfortable with auto: you either don't set PR labels and manually update version, or the other way around.

I updated the version. You set the label. We bumped twice.

But that's ok, this is a process error that results in the wrong version being applied. Only actually an issue if we release on the same version (would error out, so no harm done) or a minor instead of major (we can recover those manually and unpublish, though not great DX if we catch it late).

I'm more concerned with the CI triggers trying to re-publish on main after the merge.