3 Matching Annotations
- Sep 2020
The functionality gap between all of the bundlers has been narrowing over the years, and these days, it’s not so much functionality that matters, but rather the developer experience.
DX: start sapper project; configure eslint; eslint say that svelt should be dep; update package.json; build fails with crypt error; try to figure what the hell; google it; come here (if you have luck); revert package.json; add ignore error to eslint; Maybe we should offer better solution for this.
- dev experience
- error messages: should reveal/point to why/how error was caused and how to fix/prevent it
- useless/unhelpful/generic error messages that don't reveal why/how error was caused
- can we do even better?
- web search for something brings me here
- Dec 2019