Upgrading #javascript build configuration is always annoying. Add bundlers, transpilation and testing libraries and it becomes quite the nightmare.
And as time goes by, I'm less and less patient about this kind of stuff 😣
=> More informations about this toot | More toots from pabuisson@ruby.social
Another try, and I'm giving up once again 😭
I just can't upgrade my whole build setup to use #webpack + #typescript + #esmodules for both the app code and the test suite. Something always breaks. I lose hours reading github issues and stuff, trying stuff left and right, trying to switch to this or that, nothing works entirely, and it never breaks the same way.
That kind of nonsense will end up with me abandoning my side project 😩
=> More informations about this toot | More toots from pabuisson@ruby.social
Since I'm stubborn, I couldn't let it go. I spent more time on this yesterday evening and this morning, trying to build a very minimal project similar to mine and start the whole config from scratch: basic build, then tests, then more advanved build, then typescript.
And I got something to work. For now, my solution involves #esbuild, #typescript and #jest. With #esmodules 😍
=> More informations about this toot | More toots from pabuisson@ruby.social
[#]esbuild has a nice bonus of transpiling CSS, which will allow me to ditch the SASS dependency and write plain CSS with nested declarations.
I may still encounter issues with lib imports in my test (such as the chrome/browser specific to browser addons) but I'm confident these will be solved.
Now I "just" need to port this setup to my actual project (and surely write a blog post about this 😂)
=> More informations about this toot | More toots from pabuisson@ruby.social
text/gemini
This content has been proxied by September (3851b).