Not yet, currently it supports typescript path aliases and ESM imports/exports map. So industry standard I would say.
I don't think making plugins system is feasible because project focuses on performance. It's build in Go, so compiled language, so it's not easy to extend it like you can with JavaScript based tools.
But definitely I would like to support some reasonable amount of leading frameworks/build tools if they define some syntax / resolving mechanism that is beyond ESM specification.
I don't think making plugins system is feasible because project focuses on performance. It's build in Go, so compiled language, so it's not easy to extend it like you can with JavaScript based tools.
But definitely I would like to support some reasonable amount of leading frameworks/build tools if they define some syntax / resolving mechanism that is beyond ESM specification.