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

fix(gatsby-plugin-gatsby-cloud): fix cloud being bundled #31604

Merged
merged 1 commit into from
May 27, 2021

Conversation

wardpeet
Copy link
Contributor

Description

The gatsby-plugin-gatsby-cloud plugin has a mix of ESM & CJS which makes it difficult for webpack to figure out if sideffects are happening. We add sideEffects false to the list so wepback can remove unnecessary code
This shows that a gatsby-plugin-bundler would be a good idea.

Documentation

Related Issues

Fixes #31597

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label May 27, 2021
@wardpeet wardpeet added topic: frontend Relates to frontend issues (e.g. reach/router, gatsby-link, page-loading, asset-loading, navigation) and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels May 27, 2021
@wardpeet wardpeet added this to To cherry-pick in V3 Release Hotfixes via automation May 27, 2021
@wardpeet wardpeet merged commit 4a62a20 into master May 27, 2021
@wardpeet wardpeet deleted the fix/cloud-sideffects branch May 27, 2021 09:56
LekoArts pushed a commit that referenced this pull request May 27, 2021
@LekoArts LekoArts moved this from To cherry-pick to Backport PR opened in V3 Release Hotfixes May 27, 2021
LekoArts pushed a commit that referenced this pull request May 27, 2021
…1607)

(cherry picked from commit 4a62a20)

Co-authored-by: Ward Peeters <ward@coding-tech.com>
@LekoArts LekoArts moved this from Backport PR opened to Backported in V3 Release Hotfixes May 27, 2021
@LekoArts
Copy link
Contributor

Successfully published:
 - gatsby-plugin-gatsby-cloud@2.6.1

@LekoArts LekoArts moved this from Backported to Published in V3 Release Hotfixes May 27, 2021
moonmeister added a commit to moonmeister/gatsby that referenced this pull request Jun 1, 2021
* master: (23 commits)
  fix(gatsby-source-wordpress): Prevent "EADDRINUSE: address already in use 127.0.0.1" error (gatsbyjs#31713)
  feat(gatsby-source-wordpress: architecture.md (gatsbyjs#31537)
  chore(deps): update dependency @babel/node to ^7.14.2 (gatsbyjs#31690)
  chore(deps): update babel monorepo (gatsbyjs#31143)
  fix(gatsby): merge resolveType when merging abstract types (gatsbyjs#31710)
  chore(release): Publish next
  fix(gatsby): Correct config for svgo plugins whitelist
  chore: Add translations and validations to Contentful test (gatsbyjs#31533)
  chore(docs): Correct nginx spelling (gatsbyjs#31651)
  chore(docs): Update Jest instructions for v27 (gatsbyjs#31649)
  Fix typo in adding-search.md (gatsbyjs#31639)
  Fix typos in improving-build-performance.md (gatsbyjs#31640)
  feat(gatsby-source-wordpress): Fix false positive error if the URL and the responsePath are the same (gatsbyjs#31612)
  Fixed syntax error in example (gatsbyjs#31636)
  fix(contentful): pass reporter to retry function (gatsbyjs#31608)
  chore: Properly typecheck `gatsby` (gatsbyjs#31519)
  fix(gatsby-source-contentful): fix progress bar (gatsbyjs#31467)
  fix(gatsby-plugin-gatsby-cloud): fix cloud being bundled (gatsbyjs#31604)
  chore(gatsby-source-wordpress): Fix typos (gatsbyjs#31600)
  chore(docs): Add title to release notes (gatsbyjs#31595)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: frontend Relates to frontend issues (e.g. reach/router, gatsby-link, page-loading, asset-loading, navigation)
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

[gatsby-plugin-gatsby-cloud] Opt-in for preview indicator
2 participants