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.

Sign up for GitHub

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

Jump to bottom

plugin directory is showing removed npm packages #30058

Closed
moonmeister opened this issue Mar 6, 2021 · 1 comment
Closed

plugin directory is showing removed npm packages #30058

moonmeister opened this issue Mar 6, 2021 · 1 comment
Labels
type: bug An issue or pull request relating to a bug in Gatsby type: upstream Issues outside of Gatsby's control, caused by dependencies

Comments

@moonmeister
Copy link
Contributor

gatsby-plugin-ackee was published to NPM by mistake and replaced by gatsby-plugin-ackee-tracker. gatsby-plugin-ackee is no longer available on NPM but some how still being published into the gatsby plugin directory @ https://www.gatsbyjs.com/plugins/gatsby-plugin-ackee.

The original issue is here gatsby-uc/gatsby-plugin-ackee-tracker#69 for this package. I wouldn't be surprised if this wasn't the only case of this happening.
@moonmeister moonmeister added the type: bug An issue or pull request relating to a bug in Gatsby label Mar 6, 2021
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Mar 6, 2021
@moonmeister moonmeister changed the title plugin directory is showing removed packages plugin directory is showing removed npm packages Mar 6, 2021
@LekoArts LekoArts added type: upstream Issues outside of Gatsby's control, caused by dependencies and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Mar 8, 2021
@LekoArts LekoArts mentioned this issue Mar 8, 2021
Closed
@LekoArts
Copy link
Contributor

LekoArts commented Mar 8, 2021

Hi, thanks for the issue! We're depending on Algolia's npm search there, so it's out of our control. See: algolia/npm-search#556

I've created algolia/npm-search#586 to track this :)

@LekoArts LekoArts closed this as completed Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug An issue or pull request relating to a bug in Gatsby type: upstream Issues outside of Gatsby's control, caused by dependencies
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@moonmeister @LekoArts