-
Notifications
You must be signed in to change notification settings - Fork 154
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
Module or jsnext:main in package.json #90
Comments
Hi Dan, Can you please send a PR for that? Thanks! On Oct 5, 2016 6:10 AM, "Dan Bucholtz" [email protected] wrote:
|
Sorry, I cannot at this time. I submitted this issue to about 10-15 libs that we're seeing Ionic users use that don't follow this pattern. I don't have time, I am swamped with Ionic right now, but if you have any questions I can help as I have done this a few times now. Thanks, |
@danbucholtz can you perhaps point me at another lib which has already implemented this? |
Yes, definitely. Ionic 😄 This file covers the build portion of it. We create a temporary Our Let me know if you have any questions. It is kind of a lot to take in in someone else's repo to understand what's going on. Thanks, |
Should be fixed once #191 lands |
Since this is a Typescript app, can you distribute
es5
code (es5 target) withes2015
modules in addition to thecommonjs
modules you distribute?Set the
moduleResolution
tonode
as well to make everything work well in thetsconfig.json
.jsnext:main
andmodule
are the fields that point to the entrypoint for the es5 code with es2015 modules. Angular usesmodule
and it seems most bundlers look formodule
, thenjsnext:main
, thenmain
in that order.Thanks,
Dan
The text was updated successfully, but these errors were encountered: