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
In v2, it was possible to just install the React package. However, in v3, it seems that you also need to install the web-components package as a dependency in order for the components to render correctly
See that only the react package is installed and the alerts do not display correctly
Compare this with the following stackblitz, which also has the web-components installed (installed via npm install @ukic/web-components@next), and all is ok here
In v2 it was possible to only install the React package, as per the instructions on the guidance site, and have everything work correctly
📸 Screenshots or code
🧐 Expected behaviour
The components should work\appear correctly without needing to install the core web-components package as a dependency manually.
Additional info
seems to be caused by the fact that a v3.0.0 release is already on NPM, so where the react package has a dependency on "ukic/web-components": "^3.0.0-alpha.4", it ignores any alpha packages and instead installs that old 3.0.0 version of the web-components
maybe we could use the "next" keyword in our dependencies?
The text was updated successfully, but these errors were encountered:
Summary of the bug
In v2, it was possible to just install the React package. However, in v3, it seems that you also need to install the web-components package as a dependency in order for the components to render correctly
🪜 How to reproduce
Tell us the steps to reproduce the problem:
Compare this with the following stackblitz, which also has the web-components installed (installed via
npm install @ukic/web-components@next
), and all is ok hereIn v2 it was possible to only install the React package, as per the instructions on the guidance site, and have everything work correctly
📸 Screenshots or code
🧐 Expected behaviour
The components should work\appear correctly without needing to install the core web-components package as a dependency manually.
Additional info
seems to be caused by the fact that a v3.0.0 release is already on NPM, so where the react package has a dependency on "ukic/web-components": "^3.0.0-alpha.4", it ignores any alpha packages and instead installs that old 3.0.0 version of the web-components
maybe we could use the "next" keyword in our dependencies?
The text was updated successfully, but these errors were encountered: