You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, lexical-solid requires exact versions of all lexical dependencies. This decision was made because @lexical/react (which this package is a port of) may (need to) change concurrently with changes in the other lexical packages. So using newer lexical packages with lexical-solid would be akin to using a @lexical/react older than other lexical packages used.
However, I am now reconsidering this, to instead allow ranges of patch versions, as I think the likelihood of a newer patch version breaking an earlier @lexical/react of the same minor version is rather unlikely, and in the case it does happen, the end user could pin the packages.
This will allow users of lexical-solid to get use bug fixes from upstream lexical much faster, as they won't need to wait for this package to update and release.
The text was updated successfully, but these errors were encountered:
Currently,
lexical-solid
requires exact versions of all lexical dependencies. This decision was made because@lexical/react
(which this package is a port of) may (need to) change concurrently with changes in the other lexical packages. So using newer lexical packages withlexical-solid
would be akin to using a@lexical/react
older than other lexical packages used.However, I am now reconsidering this, to instead allow ranges of patch versions, as I think the likelihood of a newer patch version breaking an earlier
@lexical/react
of the same minor version is rather unlikely, and in the case it does happen, the end user could pin the packages.This will allow users of lexical-solid to get use bug fixes from upstream lexical much faster, as they won't need to wait for this package to update and release.
The text was updated successfully, but these errors were encountered: