how can we be sure that all of the @babel/* packages we have installed are compatible with each other?

I’m trying to debug a heady issue with babel-plugin-flow-runtime and in the process, I’m trying to make sure my @babel/* packages are up-to-date.

Annoyingly, many packages are at version 7.12.10, and some are at 7.12.12, but some are only at 7.12.1. Right now in my package.json I have:

    "@babel/cli": "^7.12.10",
    "@babel/core": "^7.12.10",
    "@babel/node": "^7.12.10",
    "@babel/plugin-proposal-class-properties": "^7.12.1",
    "@babel/plugin-proposal-decorators": "^7.12.10",
    "@babel/plugin-transform-runtime": "^7.12.10",
    "@babel/preset-env": "^7.12.10",
    "@babel/preset-flow": "^7.12.1",
    "@babel/preset-react": "^7.12.10",
    "@babel/register": "^7.12.10",

How can I verify that all of these packages are expected to work together? Compared to typescript, which is just one package, I feel like I’m standing on a house of cards.

I mean, obviously I’ve ideally gotten the latest version of each of these installed, but I still feel less secure than if it were a monolithic package.

I’m seeing weird behavior with this babel-plugin-flow-runtime issue where calling path.parentPath.get(path.listKey) (i.e. getting the Program body array path) within an ImportDeclaration enter visitor prevents the exit visitor from getting called. But so far I haven’t been able to distill it down to a simple repro. It’s hard to feel confident that the issue is coming from something babel-plugin-flow-runtime does and not from some unintended combination of @babel/* packages.

[nicolo-ribaudo]

Our goal is to make every version compatible with every other version: updating a single package shouldn’t break anything.

Sometimes we accidentally introduce incompatibilities, but when it happens we fix them.

[JLHwung]

Closing this as there are no action items and OP’s question is answered.