devtools Angular 19 peerDependency

[slcwebguy]

Hi 👋 Firstly, thank you for providing these wonderful tools. They are very much appreciated.

I'm hoping to get help with an Angular 19 upgrade that my teammates and I are attempting. At the moment, we're not able to upgrade to Angular 19 due to a peerDependency conflict in @ngneat/query-devtools@2.0.0. According to the npm registry,, version 2.0.0 of this package still expects the Angular version in use to be >=16.0.0 <19.0.0. However, the @ngneat/query@3.1.1 package doesn't have the same restriction. It has an upper-bound Angular peerDependency of <20.0.0.

I'm wondering if, perhaps, after the merging of this commit to query-3.1.1, there just wasn't an accompanying package published for devtools? Or, maybe a publish did occur but the npm registry didn't update because the devtools version number remained at 2.0.0?

I'm not sure if this peerDependency conflict is known and I want to a) bring it to your attention and b) ask if there are plans in play to update the registry for devtools?

Here are a couple of commands which show the conflicting peerDependencies at a glance:

npm info @ngneat/query@3.1.1 peerDependencies && \
  npm info @ngneat/query-devtools@2.0.0 peerDependencies

The results of these commands:

{
  '@tanstack/query-core': '^5.62.7',
  '@angular/core': '>=16.0.0 <20.0.0'
}
{
  '@angular/core': '>=16.0.0 <19.0.0',
  '@tanstack/query-devtools': '5.4.2'
}

[slcwebguy]

I didn't see this earlier. My sincere apologies. Here is a related question from my colleague, @alfredoperez...

9131e67#r151745578

[luii]

I'm wondering if, perhaps, after the merging of this commit to query-3.1.1, there just wasn't an accompanying package published for devtools?

The package wasnt published yet.

query/devtools/package.json

Line 3 in f49f3e2

"version": "2.0.0",

@NetanelBasal Can you bump the version and publish the package.

[NetanelBasal]

Done

[slcwebguy]

Oh wow! The new version, 2.1.0, is working perfectly. Thank you, both, so much.