Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
🚨 Breaking change in 2.0.34
See original GitHub issueDescription
It looks like between 2.0.33 and 2.0.34 glob was removed from Goober. Since this is a patch change, anyone pinning goober@^2.0.0 will still receive it. This just hit us for a non-mission-critical page (thankfully).
What’s Happening?
Using import { glob } from "goober" is failing when upgrading from 2.0.33 to 2.0.34.
Expected Result
Upgrading patch versions should not introduce breaking changes.
Possible Resolutions
I think the best way forward is to republish 2.0.33 as a newer version 2.0.35. Then to take the new changes up a major version since they introduce a breaking change. So tagging 2.0.34 as 3.0.0.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@jakehamilton just published
2.0.35with theglobas part of the core again. Let me know if there’s anything else.Thank you so much.
Oh, darn it 😢 totally got sidetracked and forgot that I was planning that removal 😬.
Thank you so much for your suggestions, will revert and publish
2.0.35with theglob.