Ron Spickenagel
Ron Spickenagel
@xpuu Thanks for the kind words! v4 is close, but there are a few outstanding issues I need to work out. Mainly, I need to finish the tests. As many...
Thanks for the report, @vladimiry ! I apologize for the delay. I've been pretty tied up this year. I will add support and update this thread when it's ready!
Added in [v3.4.0](https://github.com/LeDDGroup/typescript-transform-paths/releases/tag/v3.4.0). Let me know if you still have any issues.
No option at the moment. Would be pretty easy to implement, though. I'd be open to a PR as a `useExplicitIndexes` option. I was also considering adding `useExplicitExtensions`. Another esm...
> Mandatory file extensions Yep. That's the reason for the second option. Esm is a pain 😄
Eh. It should be pretty easy on both fronts, and there don't seem to be any good solutions out there for this in esm. I'll try to knock these out...
Finished. Just working on integrating with tests. I opted for adding a config property: `outputMode` which is either `commonjs` | `esm`. When not specified, it's `commonjs` by default. Behaviour is...
No problem! Documentations indicates that TS uses their own "ES-like" syntax for modules, so I think we're covered. As for map files, those should be generated post-transform. Waiting 'til tomorrow...
Sorry, I should have specified. `"outputMode": "esm"` not `useExplicitIndexes` or `useExplicitExtensions`
Is this repo public so I can take a look?