-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: tsconfig paths support #48
Labels
Comments
Yeah I agree, alias support via tsconfig.json would be great! pkgroll is about zero-config by leveraging existing configurations. PR welcome |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
error-four-o-four
added a commit
to error-four-o-four/eslint-import-resolver-typescript
that referenced
this issue
Jul 15, 2024
build failed due to * privatenumber/pkgroll#36 * privatenumber/pkgroll#48 removed 'src/tsconfig.json' relocated unit tests in 'test/unit' reconfigured 'test/tsconfig.json'
Sorry for any inconvenience caused by my lack of experience and thank you for your work. |
No inconvenience at all! Really appreciate your contribution—hope to see you contribute again! Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: