peer dependency conflict

[KernelDeimos]

Hello, I was interested to try this project out. Following the instructions I ran into a peer dependency conflict error:

[edube@iusefw16btw jesp]$ npm install
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: jsep@1.4.0
npm error Found: semantic-release@17.4.7
npm error node_modules/semantic-release
npm error   peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/changelog@5.0.1
npm error   node_modules/@semantic-release/changelog
npm error     dev @semantic-release/changelog@"^5.0.1" from the root project
npm error   peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/commit-analyzer@8.0.1
npm error   node_modules/@semantic-release/commit-analyzer
npm error     @semantic-release/commit-analyzer@"^8.0.0" from semantic-release@17.4.7
npm error     @semantic-release/commit-analyzer@"^8.0.0" from semantic-release-plus@18.4.3
npm error     node_modules/semantic-release-plus
npm error       dev semantic-release-plus@"^18.4.1" from the root project
npm error   6 more (@semantic-release/git, @semantic-release/github, ...)
npm error
npm error Could not resolve dependency:
npm error dev @semantic-release/exec@"^6.0.3" from the root project
npm error
npm error Conflicting peer dependency: semantic-release@24.2.5
npm error node_modules/semantic-release
npm error   peer semantic-release@">=18.0.0" from @semantic-release/exec@6.0.3
npm error   node_modules/@semantic-release/exec
npm error     dev @semantic-release/exec@"^6.0.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/edube/.npm/_logs/2025-06-22T06_20_28_516Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/edube/.npm/_logs/2025-06-22T06_20_28_516Z-debug-0.log

This works fine with the --legacy-peer-deps flag but I thought someone might want to know about this.

Also, to sneak in an additional question here, can I get it to stop at the right time when parsing an expression in parens? The docs suggest this expression parser can be integrated into other things (nope, I just imagined that) but I don't see how I can do that.