I like the concept, but I'm not sure if I'd use it for all Typescript projects. The types being ignored isn't an issue since that's usually checked in the development environment. However, each file is handled in isolation, so some Typescript features wouldn't work, or at least would behave differently when built by esbuild.
Far from a typescript or esbuild guru, so I'd look into this for yourself. I seem to recall one of the issues is when enums use explicit values and those values are defined in one file and used in another, for example.
That said, it works fine for what I consider "normal" usage, but my normal isn't a universal definition of normal.
As for the actual question, I've been off dealing with an ancient stack for so long that my experience with bundlers strictly academic until recently, so I don't have a favorite yet.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
esbuild is the future, now.
My favorite is actually Webpack, as it is the most reliable and customizable.
ooooooh esbuild looks pretty cool / fast!
do you advice it for both libs and apps?
any tutorial to recommend?
Actually, I haven't used it much, but I would try it in combination with Hugo.
I don't think it would support things like CSS in JS imports, or raw text file imports.
Thanks for the feedback!
Good to know, I might give it a try or at least keep a good eye on it 😉
I gave a quick try to esbuild yesterday. My first impressions summarized:
the documentation is well made. It is easy to follow and I was able to setup a proof of concept without effort.
it is really super fast! I did not try with a big lib but still, that was for sure faster.
Only thing unclear to me is if it can be used for bundling libs and apps or rather mostly/only libs.
That is something I would still need to answer.
Overall, definitely positive about it.
Thanks for sharing! 😉 This speed graph from their GitHub repo caught my attention 👀
I like the concept, but I'm not sure if I'd use it for all Typescript projects. The types being ignored isn't an issue since that's usually checked in the development environment. However, each file is handled in isolation, so some Typescript features wouldn't work, or at least would behave differently when built by esbuild.
Far from a typescript or esbuild guru, so I'd look into this for yourself. I seem to recall one of the issues is when enums use explicit values and those values are defined in one file and used in another, for example.
That said, it works fine for what I consider "normal" usage, but my normal isn't a universal definition of normal.
As for the actual question, I've been off dealing with an ancient stack for so long that my experience with bundlers strictly academic until recently, so I don't have a favorite yet.