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

chore: deprecate gatsby-plugin-guess-js #29321

Merged
merged 4 commits into from Feb 5, 2021
Merged

chore: deprecate gatsby-plugin-guess-js #29321

merged 4 commits into from Feb 5, 2021

Conversation

pieh
Copy link
Contributor

@pieh pieh commented Feb 3, 2021

plugin as-is makes heavy use of fs in ssr and also it heavily bloats bundle with all the metadata. It also use very outdated dependencies. As-is it will be incompatible with v3 and it's not clear if it's worth to migrate it

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Feb 3, 2021
wardpeet
wardpeet previously approved these changes Feb 3, 2021
@pieh pieh added type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Feb 3, 2021
plugin as-is makes heavy use of `fs` in ssr and also it heavily bloats bundle with all the metadata. It also use very outdated dependencies. As-is it will be incompatible with v3 and it's not clear if it's worth to migrate it
@wardpeet wardpeet changed the title deprecate gatsby-plugin-guess-js chore: deprecate gatsby-plugin-guess-js Feb 4, 2021
@wardpeet wardpeet merged commit 7a4b23b into master Feb 5, 2021
@wardpeet wardpeet deleted the deprecate-guess-js branch February 5, 2021 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants