You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that pkgroll is based off of package.json config - however, it would be really nice to have a build system that operates exactly like tsx. I use tsx for dev, since the watch/file execution is the fastest i've found by far. However, this means that I must use something like tsup, or ts-node for actual production building.
This is a concern for me, as tsx auto-configures, but these other libraries do not. I want as few deviations as possible between my dev environment with tsx and the production build for obvious reasons - I want a similar output format, build process, etc to reduce the chance of production-build-only bugs.
One major way to close this gap is to support tsconfig paths. Today, wildcard matching paths isn't possible with package.json.
Motivations
Closing the gap between my dev and full build process.
Alternatives
No response
Additional context
No response
Contributions
I plan to open a pull request for this issue
I plan to make a financial contribution to this project
The text was updated successfully, but these errors were encountered:
Feature request
I understand that
pkgroll
is based off of package.json config - however, it would be really nice to have a build system that operates exactly like tsx. I usetsx
for dev, since the watch/file execution is the fastest i've found by far. However, this means that I must use something like tsup, or ts-node for actual production building.This is a concern for me, as tsx auto-configures, but these other libraries do not. I want as few deviations as possible between my dev environment with tsx and the production build for obvious reasons - I want a similar output format, build process, etc to reduce the chance of production-build-only bugs.
One major way to close this gap is to support tsconfig paths. Today, wildcard matching paths isn't possible with package.json.
Motivations
Closing the gap between my dev and full build process.
Alternatives
No response
Additional context
No response
Contributions
The text was updated successfully, but these errors were encountered: