feat(posts): add blog post on swc migration #479
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
yfrommelt
left a comment
yfrommelt
left a comment
There was a problem hiding this comment.
👏 praise: Very well written! Love this article :)
fdubost
left a comment
fdubost
left a comment
There was a problem hiding this comment.
👏 Very nice post, very clear and easy to read!
|
|
||
| Ever since websites started being made essentially from Javascript, transpiling this code to run in the largest number of different browsers has been an essential step in the build process. From the very beginning, more than ten years ago, the BedrockStreaming web application has relied on [Babel](https://babeljs.io/) for this task. This year we migrated from Babel to its next gen replacement, [SWC](https://swc.rs/). It was not a smooth ride all the way, so let’s see what challenges we’ve had to overcome, and if the payoff was worth the effort ! | ||
|
|
||
| <br /> |
There was a problem hiding this comment.
Weird to not use the "default" spacing from the blog templating 👀
There was a problem hiding this comment.
I find that the default spacing is too narrow and that it doesn't look very "airy" 👀
There was a problem hiding this comment.
(to be fair, I often do the exact same thing on my own personal blog 😅)
There was a problem hiding this comment.
I understand, but it is not the "good" way to do it IMO: if you're not confortable with the current blogpost templating, then you should propose an update of the whole templating. Otherwise it breaks the design consistency of the blog. Moreover, if we migrate to another blog template one day (hope we will merge #457 one day @jpoissonnet 😅), we will inherit for this non-consistent spacing...
|
|
||
| Ever since websites started being made essentially from Javascript, transpiling this code to run in the largest number of different browsers has been an essential step in the build process. From the very beginning, more than ten years ago, the BedrockStreaming web application has relied on [Babel](https://babeljs.io/) for this task. This year we migrated from Babel to its next gen replacement, [SWC](https://swc.rs/). It was not a smooth ride all the way, so let’s see what challenges we’ve had to overcome, and if the payoff was worth the effort ! | ||
|
|
||
| <br /> |
There was a problem hiding this comment.
(to be fair, I often do the exact same thing on my own personal blog 😅)
👋🏼 Add a new article about the migration from Babel to SWC on the web project
Publication date will be modified just before merging 😊