Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Nexus conflit with @salesforcedx/design-system #762

Open
viriatis opened this issue Nov 15, 2023 · 1 comment
Open

Nexus conflit with @salesforcedx/design-system #762

viriatis opened this issue Nov 15, 2023 · 1 comment

Comments

@viriatis
Copy link

As shared in this opened issue in the link below in nexus, I am having issues using a nexus repository with a proxy to get dependencies for npm.

Npm i @salesforce-ux/design-system - Exception com.fasterxml.jackson.core.exc.StreamConstraintsException

When I try to run npm install, I get this error 500 from nexus just on this specific dependency. When I look to nexus log I see this:

com.sonatype.nexus.repository.npm.internal.orient.OrientNpmGroupDataFacet - Unable to use Cooperation to merge @salesforce-ux/design-system for repository npm                       
com.fasterxml.jackson.core.exc.StreamConstraintsException: String length (5046272) exceeds the maximum length (5000000)  

From what I see, this is related to the same issue that was fixed before on this package Version 2.21.2 (spring-23) contains a blob as readme and breaks all builds #756. The readme is broken, "contains a binary blob instead of text".

If I used an external registry like https://registry.npmjs.org, I don't have any problem, but if I used my private nexus registry, I get the error you see above.

Why? I think nexus takes a look to the general json response that come from this url https://registry.npmjs.org/@salesforce-ux/design-system/. This json has all version from this package and has the blob readme string inside making nexus to retrieve an error.

If you do a curl, you can see it:
curl https://registry.npmjs.org/@salesforce-ux/design-system/

Output:
image

It would be nice if you could fix the rest endpoint and remove the broken readme info from it or it's versions.

@dubreuil534
Copy link

Any update for this problem ?

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

No branches or pull requests

2 participants