-
Notifications
You must be signed in to change notification settings - Fork 3k
Publish different transpilation targets to different npm packages #751
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
Comments
This is a great idea. It would solve some of the other issues we've seen with people on older versions of npm as well. |
So I think |
Awesome, unless someone has already started work on this (@robwormald), I'll get to work once I wrap up another issue I'm working on in angular. |
i can do this if you like @jeffbcross |
i dont think we need the TS distro either - just distribute the |
Perhaps it should be |
... then again that could imply |
SystemJS et al refer to it as |
What about |
@trxcllnt: I discussed this on Slack with @jeffbcross, and he brought up a good point on the |
I also like the idea of CJS being the default, non-suffixed (rxjs) distribution, since it is in the current native format of node modules (CJS). |
Closed by @robwormald in 185abdf (Issues have been opened to fix bugs introduced in the new process) |
In order to have nicer import paths, without
dist
and module/language directories, we should publish the different outputs (CJS, ES6, TS) as different npm packages: rxjs for CJS, rxjs-es6 for ES6, rxjs-ts for TypeScript. It would also be nice to drop the@reactivex
scoping in the process, since that causes issues for users with older npm versions.Before:
After (though #750 will move the operators even further up the export tree)
The text was updated successfully, but these errors were encountered: