-
Notifications
You must be signed in to change notification settings - Fork 22
Need updated topology dependencies #274
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
Comments
@jpinsonneau
which should mean that you can use any 6.x version of We use semver this way because it means that people can pull in changes to extensions like topology without needing to necessarily bump to higher versions of |
Digging into Which contains a $ npm explain @patternfly/react-core
@patternfly/[email protected]
node_modules/@patternfly/react-core
@patternfly/react-core@"^6.2.0-prerelease.18" from the root project
@patternfly/react-core@"^6.2.0-prerelease.18" from @patternfly/[email protected]
node_modules/@patternfly/react-drag-drop
@patternfly/react-drag-drop@"^6.2.0-prerelease.20" from the root project
@patternfly/react-core@"^6.2.0-prerelease.18" from @patternfly/[email protected]
node_modules/@patternfly/react-table
@patternfly/react-table@"^6.2.0-prerelease.19" from the root project
@patternfly/[email protected]
node_modules/@patternfly/react-topology/node_modules/@patternfly/react-core
@patternfly/react-core@"^6.0.0" from @patternfly/[email protected]
node_modules/@patternfly/react-topology
@patternfly/react-topology@"^6.2.0-prerelease.3" from the root project FYI I'm using |
Comparing to other @patternfly packages you can see that react-topology is not importing the right dependencies: |
Ah - I think I see. If you are trying to pull in a patternfly prerelease to your codebase, I think semver is going to run into some problems. PatternFly is approaching a code freeze and release of 6.2.0 at the end of March and if you pull in the This is something we see often - when we are testing prereleases as release candidates in product code bases, we often have to add a resolution to the package.json file in order to avoid this exact issue with multiple versions of patternfly packages. Semver is doing some sort of version pattern matching and is not able to determine that Once all the patternfly dependency versions in a codebase are updated to drop any |
I'm sorry @nicolethoen but this is not related to prerelease. I followed your suggestion and changed all my dependencies to PF 6.1.0:
And the result is still the same:
So I confirm there is a dependecy versions issue, only with react-topology package. |
Hi @jpinsonneau. It looks like you are looking at the package.json for the topology release in the node_modules directory. Having the ^6.0.0 is fine it will use anything that is a patch release greater then 6.0.0. This should resolve to 6.1.0 if the other packages you have are require that. If you look at the version in the package.json is pulling down 6.1.0 for topology. Here is a vite app that will pull down react-core, react-topology, and patternfly 6.1.0. https://github.com/dlabaj/myPFTestApp If you do an npm install and look at the version of the packages that where pull down they are 6.1.0 for all packages. Thanks. |
Closing for now based on the an example above. If this is still an issue, feel free to reopen it with some additional comments. It should be pulling in the correct version, if not we can reevaluate what's causing the problem. |
@patternfly/react-topology is not updated since 6.1.0 and imports the old core dependency which uses useId hook that is not supported by React 17
See patternfly/patternfly-react#11351 (comment)
The text was updated successfully, but these errors were encountered: