-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
Document installing plugin@next #3756
Comments
We indeed want to align versions, the error is on-purpose fail-fast behavior to avoid more nasty issues due to incompatible versions. According to you, what changes should be made to the docs to make this clearer? Alpha 66 version is published under the "next" tag. https://www.npmjs.com/package/@docusaurus/plugin-ideal-image |
"NOTICE: To circumvent npm errors due to incompatible versions installed between core and plugins, we advise to install all packages at version "next". Example:
Maybe something like this? |
Hi
Last release used the latest tag
We're going to remove @next refs from the doc
Can you confirm it works better for you now?
Le mar. 17 nov. 2020 à 18:52, Maurice Faber <[email protected]> a
écrit :
… "NOTICE: To circumvent npm errors due to incompatible versions installed
between core and plugins, we advise to install all packages at version
"next". Example:
npm install -S @***@***.*** @***@***.***"
Maybe something like this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3756 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFW6PXD2QEWGYTYGSB3YGLSQKZ6XANCNFSM4TWKCEEA>
.
|
It looks like it work as expected now, you don't need the next tag anymore to get latest packages |
📚 Documentation
It took me some time to figure out that installing a plugin as documented was giving me errors (See #3755 ) because the version would not match core. Example:
This would install the latest published version of the plugin, which was
2.0.0-alpha.37
at the time of writing.It turns out that installing a plugin
@next
somehow does install it at core version, which I did not see documented here: https://v2.docusaurus.io/docs/using-plugins/Example:
After doing that I see version
2.0.0-alpha.66
of the plugin installed (which is strange as it is not published).Have you read the Contributing Guidelines on issues?
Yes
The text was updated successfully, but these errors were encountered: