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

Fix yarn support #27

Open
andrew opened this issue Feb 2, 2021 · 1 comment
Open

Fix yarn support #27

andrew opened this issue Feb 2, 2021 · 1 comment
Labels
bug Something isn't working enhancement New feature or request help wanted Extra attention is needed

Comments

@andrew
Copy link
Member

andrew commented Feb 2, 2021

Currently forest doesn't support yarn because yarn always makes https requests to the registry regardless of what options you've set (see yarnpkg/yarn#7393).

The solution is to properly support https requests via the proxy, which requires configuring certificates and such.

@andrew andrew added bug Something isn't working enhancement New feature or request labels Feb 2, 2021
@andrew
Copy link
Member Author

andrew commented Apr 14, 2021

Now that #32 is fixed, this should be fixed, but yarn v1 doesn't ignore the domain on the registry field like npm does so it skips loading tarballs from localhost and goes straight back to the registry.

It doesn't cause yarn to fail anymore, but it doesn't cache anything onto ipfs either.

In theory this is fixed in yarn v2, I've not tested that yet, but also I'm not sure if many people are using yarn v2 yet either.

@andrew andrew added the help wanted Extra attention is needed label Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant