💥 Proposal
https://www.npmjs.com/package/upath#why
It could be less painful to ensure Windows support if all paths where using posix style (/ separator) instead of being platform dependent.
Windows/NodeJS is able to understand both / and \\ so it would be nice to normalize on all paths on posix style.
This could prevent issues we often see after committing, when the CI (build or tests) fails but only on Windows, such as:

My idea would be to:
- Use "upath" everywhere
- Use
upath.normalize() everywhere instead of our custom posixPath() fn.
- Prevent "path" from being imported with an ESLint rule
💥 Proposal
https://www.npmjs.com/package/upath#why
It could be less painful to ensure Windows support if all paths where using posix style (
/separator) instead of being platform dependent.Windows/NodeJS is able to understand both
/and\\so it would be nice to normalize on all paths on posix style.This could prevent issues we often see after committing, when the CI (build or tests) fails but only on Windows, such as:
My idea would be to:
upath.normalize()everywhere instead of our customposixPath()fn.