Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mikro-orm packages should depend on exact versions for other mikro-orm packages #4764

Closed
stefansundin opened this issue Sep 30, 2023 · 1 comment

Comments

@stefansundin
Copy link
Contributor

Describe the bug

Hello. I'm having trouble installing mikro-orm version 6.0.0-dev.108. I noticed that not all packages have 6.0.0-dev.109 published, so I want to use 108 for the time being.

The dependencies in my package.json:

    "@mikro-orm/cli": "6.0.0-dev.108",
    "@mikro-orm/core": "6.0.0-dev.108",
    "@mikro-orm/migrations": "6.0.0-dev.108",
    "@mikro-orm/postgresql": "6.0.0-dev.108",

However, even though I am depending on the exact versions like above, the packages themselves are pulling in a newer version of each other, resulting in a mess in my yarn.lock file.

Of these four packages, only @mikro-orm/core have an 109 version published, but @mikro-orm/knex is also pulled in with version 109.

Stack trace

When I try to run my app, I get this error:

Error: Bad @mikro-orm/cli version 6.0.0-dev.108.
All official @mikro-orm/* packages need to have the exact same version as @mikro-orm/core (6.0.0-dev.109).
Only exceptions are packages that don't live in the 'mikro-orm' repository: nestjs, sql-highlighter, mongo-highlighter.
Maybe you want to check, or regenerate your yarn.lock or package-lock.json file?

To Reproduce

Steps to reproduce the behavior:

  1. Try to install 6.0.0-dev.108 as described above.
  2. Run the app.
  3. See the error.

Expected behavior

I expect mikro-orm packages to depend on exact versions of each other so that I can consistently install a version that isn't the latest version.

Additional context

I am not able to figure out the correct "resolutions" or "override" syntax to use to override the transient version dependencies.

Packages missing a 109 release: @mikro-orm/cli, @mikro-orm/postgresql, @mikro-orm/migrations.

Thanks!

Versions

Dependency Version
node 18.18.0
typescript 5.1.6
mikro-orm 6.0.0-dev.108
@stefansundin stefansundin changed the title mikro-orm packages dependency should depend on exact versions for other mikro-orm packages mikro-orm packages should depend on exact versions for other mikro-orm packages Sep 30, 2023
@B4nan
Copy link
Member

B4nan commented Sep 30, 2023

Yeah agreed, we should make this change, it's not just about the constant NPM hiccups, causing some packages to be missing (as they decide to throw a 503 at us in the middle of the publishing, this is also problematic for people who simply want to use some older version.

@B4nan B4nan closed this as completed in f4868ed Sep 30, 2023
B4nan added a commit that referenced this issue Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants