Error With Fedify-CLI Init

[LithiumSource]

Hello, could you please help me with this error.

# npm resolution error report

While resolving: undefined@undefined
Found: @fedify/fedify@1.5.1
node_modules/@fedify/fedify
  @fedify/fedify@"^1.4.8" from the root project

Could not resolve dependency:
peer @fedify/fedify@">=0.12.0, <1" from @fedify/express@0.1.4
node_modules/@fedify/express
  @fedify/express@"^0.1.3" from the root project

Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

[ThisIsMissEm]

@dahlia I can reproduce this on npm version 10.9.2, and specifically, when installing individually each dependency, I cannot reproduced.

However, if I run the command that fedify init would use, then it would be these:

$ echo "{}" > package.json
$ npm add @fedify/fedify@1.5.1 @logtape/logtape@^0.8.2 express@^4.19.2 @fedify/express@^0.1.3 @dotenvx/dotenvx@^1.14.1 tsx@^4.17.0

and this does fail with the error above.

It does work if I change it to include --legacy-peer-deps:

$ npm add @fedify/fedify@1.5.1 @logtape/logtape@^0.8.2 express@^4.19.2 @fedify/express@^0.1.3 @dotenvx/dotenvx@^1.14.1 tsx@^4.17.0 --legacy-peer-deps

I suspect part of the issue is this semver range, which doesn't look quite right:

"peerDependencies": {
    "@fedify/fedify": ">=0.12.0, <2"
  },

Since it doesn't seem like a valid range: https://jubianchi.github.io/semver-check/#/%3E%3D0.12.0%2C%20%3C2/1.5.1

However, without the comma it is: https://jubianchi.github.io/semver-check/#/%3E%3D0.12.0%20%3C2/1.5.1

The other option that would work is doing two installs:

1. for fedify & logtape
2. for initializer packages

This does still complain:

$ npm add express@^4.19.2 @fedify/express@^0.1.3 @dotenvx/dotenvx@^1.14.1 tsx@^4.17.0 --force                
npm warn using --force Recommended protections disabled.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @fedify/express@0.1.4
npm warn Found: @fedify/fedify@1.5.1
npm warn node_modules/@fedify/fedify
npm warn   @fedify/fedify@"^1.5.1" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer @fedify/fedify@">=0.12.0, <1" from @fedify/express@0.1.4
npm warn node_modules/@fedify/express
npm warn   @fedify/express@"^0.1.3" from the root project
npm warn
npm warn Conflicting peer dependency: @fedify/fedify@0.15.9
npm warn node_modules/@fedify/fedify
npm warn   peer @fedify/fedify@">=0.12.0, <1" from @fedify/express@0.1.4
npm warn   node_modules/@fedify/express
npm warn     @fedify/express@"^0.1.3" from the root project

added 102 packages, and audited 152 packages in 3s

34 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

But doesn't fail.

[ThisIsMissEm]

@dahlia that's all a long way to say that I suspect updating the peerDependencies range in @fedify/express to not have the comma will fix the issue.

[ThisIsMissEm]

Have opened a potential fix: fedify-dev/express#3

[dahlia]

Oops, I must've gotten that mixed up with the version constraint syntax from Python packaging. Or maybe Haskell's? Anyway, thanks for the debugging!

[dahlia]

Just released @fedify/express 0.2.1, which probably fixes this!

@YugenSource Could you try it again?

[ThisIsMissEm]

Still fails because fedify init is using a version range constrain of ^0.1.3 which is only satisfied by >=0.1.3 <0.2.0-0: https://jubianchi.github.io/semver-check/#/^0.1.3/0.2.1

Opened #231 to fix.

[dahlia]

Okay, I've just released Fedify v1.5.2 which includes @ThisIsMissEm's patch #231. It should be fixed now.

@YugenSource Please upgrade your Fedify CLI to v1.5.2 and try it again!