Skip to content

Conversation

@guybedford
Copy link
Contributor

As discussed in #18 it may make more sense to double-down on a unique main property if we can't guarantee that automatic file extension adding will be included for the ES resolver.

It just seems to hinge on too many compatibility decisions to assume this will work out at this stage. If it does work out eventually, great though. But let's not make bets.

@guybedford
Copy link
Contributor Author

Updated to add a clause to note using "module" could be a possibility subject to compatibility testing.

@zenparsing
Copy link
Owner

I tend to agree, and feel pretty good about "default" in package.json at this point.

@zenparsing zenparsing merged commit e32e263 into zenparsing:master Jun 25, 2018
@zenparsing zenparsing mentioned this pull request Jun 25, 2018
@guybedford
Copy link
Contributor Author

@zenparsing do you also agree here that if we test this implementation with "module" in place of "default" and it works out in some wide initial testing, "module" can still be considered?

@zenparsing
Copy link
Owner

I agree. Both "module" and "default" seem acceptable to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants