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: uuid major upgrade #26636

Merged
merged 1 commit into from
Aug 27, 2020
Merged

Chore: uuid major upgrade #26636

merged 1 commit into from
Aug 27, 2020

Conversation

herecydev
Copy link
Contributor

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Aug 25, 2020
@herecydev herecydev changed the title Upgrade uuid Chore: uuid major upgrade Aug 25, 2020
@pvdz
Copy link
Contributor

pvdz commented Aug 26, 2020

@herecydev can you confirm that the bundle did not grow to include the entire uuid library? There are two cases in the PR where v4 is required rather than imported and since their changelogs explicitly mention tree shaking as a reason for no longer exposing deep imports, I'd also want to make sure the whole library unnecessarily reaches the front end. That would be bad :)

@pvdz pvdz added topic: npm* and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Aug 26, 2020
@herecydev
Copy link
Contributor Author

I'll do my best to work that out

@herecydev
Copy link
Contributor Author

Peter, just so I'm clear are you talking about uuid being in the commons bundle? If so, I don't think it'll ever get bundled as it's only used in the "gatsby-node" side of gatsby if that makes sense. I double checked in the bundle but couldn't see anything in there relating to uuid

@pvdz
Copy link
Contributor

pvdz commented Aug 27, 2020

Great, thanks :)

@pvdz pvdz merged commit dbe6767 into gatsbyjs:master Aug 27, 2020
@vladar
Copy link
Contributor

vladar commented Aug 28, 2020

Published in gatsby@2.24.52

pvdz added a commit that referenced this pull request Sep 8, 2020
The bump to v8 as applied in #26636 gave us no benefits and are giving problems with imports in certain cases. Maintainers have made it clear they won't offer any support for node 13, which we will want to support for a while as well.

In due time we'll replace this library with something simpler as the maintenance burden will be too high. For now we revert and pin to 3.4.0, the last stable version that does what we want.

Fixes #26812
@pvdz
Copy link
Contributor

pvdz commented Sep 8, 2020

This change is being reverted in #26824 because the ESM changes applied in v7/v8 are causing problems and we're not expecting support from the maintainers. Additionally, there's no real benefit from bumping the dep version so we're just gonna pin it to 3.4.0 and move on, ultimately replacing it with something custom. In all use cases of this library we mostly care about generating a random string, not an actual uuid.

gatsbybot pushed a commit that referenced this pull request Sep 8, 2020
The bump to v8 as applied in #26636 gave us no benefits and are giving problems with imports in certain cases. Maintainers have made it clear they won't offer any support for node 13, which we will want to support for a while as well.

In due time we'll replace this library with something simpler as the maintenance burden will be too high. For now we revert and pin to 3.4.0, the last stable version that does what we want.

Fixes #26812
pragmaticpat pushed a commit to pragmaticpat/gatsby that referenced this pull request Apr 28, 2022
…s#26824)

The bump to v8 as applied in gatsbyjs#26636 gave us no benefits and are giving problems with imports in certain cases. Maintainers have made it clear they won't offer any support for node 13, which we will want to support for a while as well.

In due time we'll replace this library with something simpler as the maintenance burden will be too high. For now we revert and pin to 3.4.0, the last stable version that does what we want.

Fixes gatsbyjs#26812
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants