Adding Semantic Release to an old Babel Plugin [Live] (2/2)
In the second part of the live coding with babel-plugin-ignore-html-and-css-imports package I'm adding the Semantic Release through Github Actions to it. There is a few gotchas when doing so to a package that already has a release on npm, and I'm walking through them here.
(Sorry for the sound quality in the first clip, it gets better the moment I start coding! (still in the video-making learning mode :) )
Let me know if you have any questions or thoughts in the comments below.
Let us help you on your journey to Quality Faster
We at Xolv.io specialize in helping our clients get more for less. We can get you to the holy grail of continuous deployment where every commit can go to production — and yes, even for large enterprises.
Feel free to schedule a call or send us a message below to see how we can help.
Better way to use useReducer with TypeScript
Introducing useComplexState hook, - a small wrapper combining Redux Toolkit, useReducer with some extra syntax sugar to make things even simpler and more to-the-point.
Dealing with randomness in tests
A few patterns to help you deal with randomness in your codebase.
How to deal with the yarn link "There's already a package called x registered" error
Short discussion about helpful error messages, and a solution to the problem