We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
NPMJS already tells you how to install with NPM.
However installing with yarn might not be so straightforward.
After quite a bit of fiddling around with an instance of yarn 4 berry, I seem to have finally succeeded in installing from Github packages like this:
yarn 4 berry
yarn add @johnrdorazio/jquery-clock-plugin@https://github.com/johnrdorazio/jquery-clock-plugin
And I'm still not sure how much the following two files had any effect on the installation process:
//.npmrc registry=https://registry.npmjs.org/ @johnrdorazio:registry=https://npm.pkg.github.com/
//.yarnrc.yml npmScopes: "johnrdorazio": npmRegistryServer: "https://npm.pkg.github.com"
However I haven't yet tested implementing within a project just yet.
It certainly is simpler to include from npmjs:
yarn add jquery-clock-plugin
In any case, once it's all tested and implemented, info should be added to the readme.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
NPMJS already tells you how to install with NPM.
However installing with yarn might not be so straightforward.
After quite a bit of fiddling around with an instance of
yarn 4 berry
, I seem to have finally succeeded in installing from Github packages like this:yarn add @johnrdorazio/jquery-clock-plugin@https://github.com/johnrdorazio/jquery-clock-plugin
And I'm still not sure how much the following two files had any effect on the installation process:
However I haven't yet tested implementing within a project just yet.
It certainly is simpler to include from npmjs:
yarn add jquery-clock-plugin
In any case, once it's all tested and implemented, info should be added to the readme.
The text was updated successfully, but these errors were encountered: