-
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
add script to copy types for commonjs module system #184
Conversation
I just tested the script, but Haven't tried to publish it. |
@shrujalshah28 Let's focus the review here, and drop https://github.com/js-temporal/temporal-polyfill/pull/181/files as is duplicated with this. |
Based on the way other projects are fixing their types for Node's ESM support, I think this is the right fix. Once the key is included for the default this should be good to merge. @shrujalshah28 if you have a repo setup to use Node's ESM support that I can use to verify this fixes things, that would be most helpful. |
@12wrigja Currently I use ESM in private repository but tomorrow I can create small repository to verify changes. |
Thanks. I'd be especially interested to see if it's different from the repro in #177 (comment) - I think this is the same problem / fix, but want to be sure. |
With your repro repo, I think we would also need fixes to JSBI (our only dependency) in order for this to work - without also changing the JSBI package.json, the temporal project doesn't seem to compile anymore:
JSBI's package.json is set up a bit differently than ours and doesn't have exports at all. I'm wondering whether introducing exports could be a breaking change. |
Ohh, I am not an expert on this but I will try this and find the solution.
Yes |
I'm also an owner for JSBI, so I'll chat with the other maintainers over the next couple days and see if we can fix JSBI up as well. It's very unfortunate that this has a transitive effect on the ecosystem. |
@12wrigja When I try to build in my branch, It works fine. I am able to build packages.
|
I couldn't find a way to repro the error I saw above in local testing when patching your repro and this branch, so I think we are good to merge this. Thanks for your help figuring this out! |
Fix: #177