Skip to content
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

Package manager documentation only covers npm and yarn v1, not yarn v2 #19035

Closed
unikitty37 opened this issue May 12, 2022 · 1 comment
Closed

Comments

@unikitty37
Copy link

The documentation at https://fontawesome.com/v5/docs/web/setup/use-package-managers states

If you'd prefer a per-project setting (great for teams and CI/CD), create a .npmrc file in the root of your project (or where you have your package.json file):

but the docs for Yarn 2 at https://yarnpkg.com/getting-started/migration#update-your-configuration-to-the-new-settings state

Yarn doesn't use the configuration from your .npmrc files anymore; we instead read all of our configuration from the .yarnrc.yml files whose available settings can be found in our documentation.

There is no documentation on what the .yarnrc.yml equivalents are of the given .npmrc values. (This is also true for the current v6 documentation.)

As this is only needed for the non-free version of FontAwesome, this is only affecting paying customers, who shouldn't have to scratch around working it out for themselves. Please could the documentation be updated to show Yarn 2 users how to load FontAwesome properly?

@unikitty37
Copy link
Author

This appears to be a duplicate of #16156. Mind, that is two years old and the docs still don't cover Yarn 2!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant