Need new version for Nx@18

[kylebjordahl]

Current Behavior

Cannot add @nxlv/python plugin to workspace with Nx 18

Expected Behavior

Plugin installs

Steps to Reproduce

1. npm install @nxlv/[email protected]

Nx Report

NX   Report complete - copy this into the issue template

Node   : 20.11.1
OS     : darwin-arm64
npm    : 10.2.4

nx                 : 18.0.6
@nx/js             : 18.0.6
@nx/linter         : 18.0.6
@nx/eslint         : 18.0.6
@nx/workspace      : 18.0.6
@nx/cypress        : 18.0.6
@nx/devkit         : 18.0.6
@nx/eslint-plugin  : 18.0.6
@nx/react          : 18.0.6
@nx/remix          : 18.0.6
@nrwl/tao          : 18.0.6
@nx/vite           : 18.0.6
@nx/web            : 18.0.6
typescript         : 5.3.3

Failure Logs

Executing task: npm install  @nxlv/[email protected] 

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @kb_nx_architect/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/nx
npm ERR!   dev nx@"18.0.6" from the root project
npm ERR!   peer nx@">= 16 <= 18" from @nx/[email protected]
npm ERR!   node_modules/@nx/devkit
npm ERR!     peer @nx/devkit@"^17.0.0" from @nxlv/[email protected]
npm ERR!     node_modules/@nxlv/python
npm ERR!       @nxlv/python@"17.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer nx@"^17.0.0" from @nxlv/[email protected]
npm ERR! node_modules/@nxlv/python
npm ERR!   @nxlv/python@"17.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /Users/kyle/.npm/_logs/2024-03-03T00_35_14_316Z-eresolve-report.txt

Additional Information

Per release notes, v18 was a major release due to Project Crystal, but contains no breaking changes. Support for v18 in this plugin should be a simple as fixing the peer dependency.

While this can be circumvented with --force that leads to errors/warnings on subsequent NPM installs.