For 1 yes, its only the ws module which gives error of 403.For 2, I am not able to access the page using my domain credentials. The .npmrc file has the credentials.For 3, the version is present in package-lock.json, I will need to first host it on JFrog first?"node_modules/ws": { "version": "8.16.0...

The permission issue should have been valid for all the other artifacts too.

There is a npmrc file which is configured and downloading artifacts for other node modules but only this one for web socket is giving an issue.

i'm able to download other assets from jfrog in ui.frontend and its part of the build so any particular reason why this would be an issue?

hi all, I joined a project where jfrog is used as repo manager for hosting artifacts.When giving a build we got the following error - [INFO] npm ERR! code E403[INFO] npm ERR! 403 403 Forbidden - GET https://<<clientDomain>.jfrog.io/artifactory/api/npm/customer-experience-management-npm-virtual/ws/-/...

hi all, we ran a BPA report on AEM 6.5.18 for migrating to cloud for our project.The BPA report lists non-compatible content as follows - Say we made a change on node "test" present under /a/b/c/test The BPA reports the issue for the nested child as follows - /a, /a/b, /a/b/c, /a/b/c/test - A single...