-
Notifications
You must be signed in to change notification settings - Fork 19
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
[Feature Request] Expose modules without lib/es6 prefix #32
Comments
I'm wondering maybe #29 already fixed the tree shaking part and the only thing needs to be done for this issue is to build the targets directly instead of being under |
Hey @CYBAI, sorry for not getting back to you sooner on this. The issues surrounding tree-shakability were handled with #29 when The issue you are raising I think has more to do with the import ergonomics of the library. I would be happy to work on implementation of direct imports for
@gcanti - sorry to ping you once again, but would you mind weighing in on the above? If a utility library is desired, I am happy to work on implementation. Otherwise, I will just port over the scripts from |
@gcanti thank you so much!!!!!!!!!!!!!! |
🚀 Feature request
Current Behavior
As a
parser-ts
user, I will need to import modules likeparser-ts/lib/Parser
orparser-ts/es6/Parser
.Desired Behavior
Ideally, it would be great to just import the module directly without prefix like
parser-ts/Parser
thatfp-ts
already shipped in 2.8.0.Suggested Solution
Maybe we can follow what
fp-ts
has done in gcanti/fp-ts#1241 to fix this.Who does this impact? Who is this for?
parser-ts
usersDescribe alternatives you've considered
Additional context
Your environment
(I also filed another similar issue for
fp-ts-contrib
at gcanti/fp-ts-contrib#67)The text was updated successfully, but these errors were encountered: