Open JoshMcCullough opened 1 year ago
Hi!
ckeditor-react
essentially is asking for any version>=37
but this is a peerDependency which means it's not automatically installed in some cases:
npm versions 1, 2, and 7 will automatically install peerDependencies if they are not explicitly depended upon higher in the dependency tree.
I think --legacy-peer-deps
is a workaround right now, and it should disable the installation of peer deps. We will take a look at this issue when discussing the future of predefined builds. cc @filipsobol
There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may still be relevant, so if you're interested in the solution, leave a comment or reaction under this issue.
Two-part question:
@ckeditor/ckeditor5-engine
where moved fromdependencies
todevDependencies
. It seems that these should be actual deps since they are not used as part of the build process. This is causing issues, because of ...ckeditor-react
is using>=
for the semver versioning ofckeditor-react
. So when I install our custom CKE inline build into our consuming app, NPM tries to install@ckeditor/ckeditor5-engine@40.0.0
even though we are not yet on v40. What seems to be happening isckeditor-react
essentially is asking for any version>=37
, so NPM selects v40, not knowning that our custom build requires^38.0.1
-- since it's in there as adevDependency
(as it is in all of the CKE packages I checked).Here's what the failed install looks like:
Note that we cannot agree on which version of
@ckeditor/ckeditor5-engine
to install.📃 Other details
If you'd like to see this improvement implemented, add a 👍 reaction to this post.