This message was deleted.
# report-bugss
Slackbot
07/19/2023, 5:15 PMThis message was deleted.
j
Jacob Gold
07/19/2023, 5:17 PMWe didn’t remove old versions from NPM intentionally, let me look into what happened there.
Jacob Gold
07/19/2023, 5:17 PMWhat error are you seeing?
i
Ian Gudger
07/19/2023, 5:27 PMIf you check the versions tab, only the current version is listed on NPM.
This is the error we are getting in our logs:
Copy code
error An unexpected error occurred: "<https://registry.yarnpkg.com/@withgraphite/graphite-cli/-/graphite-cli-0.20.22.tgz>: Request failed \"404 Not Found\"".Ian Gudger
07/19/2023, 5:31 PMIt would be great if the old versions could be restored so we build old versions of our code again.
j
Jacob Gold
07/19/2023, 5:55 PMhmm, unfortunately NPM doesn't seem to be letting me fix this by republishing our old versions. I am reaching out to their support team to see if we can get them restored.
Jacob Gold
07/19/2023, 5:56 PMOut of curiousity, why does your code have a dependency on the graphite-cli? It's generally intended for use as a user-invoked CLI tool
i
Ian Gudger
07/19/2023, 6:07 PMWe depend on it as a dev dependency. It was the easiest way to integrate the tool into our development environment.
j
Jacob Gold
07/19/2023, 6:07 PMah i see
Jacob Gold
07/19/2023, 6:08 PMVery sorry about the inconvenience, did bumping the version fix everything or is there anything else here that we might need to help with?
i
Ian Gudger
07/19/2023, 6:09 PMYou still need to update your cli install docs as they still say to use the GitHub repo.
j
Jacob Gold
07/19/2023, 6:09 PMAh, right — thanks!
i
Ian Gudger
07/19/2023, 6:12 PMWe were in the process of switching from using the GitHub repo to NPM because of the process of updating the CLI. With NPM, we can update the code in our mono repo and once everyone syncs and rebuilds, they have the updated tool. That is why both changes caused trouble for us.