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

Frontend npm install problems (lyft repository dependencies) #2141

Open
wuttem opened this issue Apr 15, 2023 · 11 comments
Open

Frontend npm install problems (lyft repository dependencies) #2141

wuttem opened this issue Apr 15, 2023 · 11 comments
Labels
area:frontend From the Frontend folder stale status:in_progress Issue that is being worked on right now type:bug An unexpected problem or unintended behavior

Comments

@wuttem
Copy link

wuttem commented Apr 15, 2023

I was trying to build the static part of the amundsen frontend like outlined in the documentation

cd static
npm install
npm run build

This leads to a E401 errors from npm.

Current Behavior

Some of the dependencies in package-lock.json are resolved to a repository hosted by lyft.
This leads to problems building because it seems this is not open for public.

Example:
react-switch is resolved to https://artifactory-npm.lyft.net/artifactory/api/npm/virtual-npm-lyft/react-switch/-/react-switch-6.0.0.tgz which requires some kind of login to access.

Not sure what the reason for this is, but it seems like all of these dependencies could also be resolved by a public repository.

For Example
react-switch could be resolved from https://registry.npmjs.org/react-switch/-/react-switch-6.0.0.tgz

Possible Solution

It is of course possible to delete package-lock.json and rebuild it however this makes it much more complicated to get a working configuration. Manually changing the file for just a couple of dependencies is also not a great solution.

My proposal would be to change package-lock.json to only resolved dependencies to public available repositories.

@wuttem wuttem added status:needs_triage For all issues that need to be processed type:bug An unexpected problem or unintended behavior labels Apr 15, 2023
@boring-cyborg
Copy link

boring-cyborg bot commented Apr 15, 2023

Thanks for opening your first issue here!

@mikaalanwar
Copy link
Contributor

I came across this issue once as well and saw some occurrences of people facing this in the amundsen slack channel too ...

@stale
Copy link

stale bot commented May 3, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label May 3, 2023
@wuttem
Copy link
Author

wuttem commented May 5, 2023

This might be a nitpick, but to me, the "stale bot" does not seem to make a lot of sense. It just makes it obvious that replies are taking some time... Which I am totally ok with, by the way. Why shouldn't it be ok if there is no reply to an issue for 2 weeks ? Does not seem like auto closing issues helps with anything.

@stale stale bot removed the stale label May 5, 2023
@stale
Copy link

stale bot commented May 20, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label May 20, 2023
@rjalan01
Copy link

rjalan01 commented Jun 5, 2023

It is still happening, it is connecting to https://artifactory-npm.lyft.net/artifactory/api/npm/virtual-npm-lyft/tree-changes/-/t
ree-changes-0.7.1.tgz which need lyft credential. please prioritise it

@stale stale bot removed the stale label Jun 5, 2023
@stale
Copy link

stale bot commented Jun 23, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Jun 23, 2023
@Golodhros
Copy link
Member

Definitely a bug.
I will prioritize this, thanks for your patience!

@stale stale bot removed the stale label Jul 7, 2023
@Golodhros Golodhros added status:in_progress Issue that is being worked on right now area:frontend From the Frontend folder stale and removed status:needs_triage For all issues that need to be processed labels Jul 7, 2023
@stale stale bot removed the stale label Jul 7, 2023
@Golodhros
Copy link
Member

Check #2174 for a fix

@rjalan01
Copy link

rjalan01 commented Jul 8, 2023

Thank you for the fix

@stale
Copy link

stale bot commented Aug 7, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:frontend From the Frontend folder stale status:in_progress Issue that is being worked on right now type:bug An unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

4 participants