@jdalton @sindresorhus @rauschma @IgorMinar @TheLarkInn @kentcdodds @dan_abramov @Rich_Harris
Hello fellow open source publishing/bundling folks... I want to start a public discussion about the current "state of the art" for libraries publishing JavaScript modules... 1/6
-
Show this thread
-
Basically, RxJS is going to undergo (mostly cosmetic) changes over these next few months, and I think it's a good time for us to revisit our strategy for publishing different module types. 2/6
1 reply 0 retweets 3 likesShow this thread -
Currently, RxJS is publishing: ESM5, ESM2015, CJS, and a single "kitchen-sync" UMD (for classic global script-tag style imports), as well as TypeScript source files for source mapping. Honestly, it's a little out of control. 3/6
3 replies 1 retweet 3 likesShow this thread -
In your _opinion_, where are we headed? When will be the proper time to just publish ESM2015 (with extensions or whatever we need to do) and forgo building CJS/ESM5 etc? 4/6
1 reply 0 retweets 1 likeShow this thread -
With the advent of things like
@codesandbox,@stackblitz, and@unpkg, is it even necessary that we publish big UMD globals anymore? 5/62 replies 0 retweets 3 likesShow this thread -
Replying to @BenLesh
UMD hasn’t been necessary for years. just publish es5 cjs main, and optionally ESM if you really want to
1 reply 0 retweets 1 like -
Replying to @ljharb
Angular is a major consumer of RxJS, and I'm sure they'll want ES2015 for differential loading. ESM is also a must for tree-shaking.
1 reply 0 retweets 1 like -
Replying to @BenLesh
there’s no technical reason why cjs can’t be identically tree-shaken, and the real fix for treeshaking is deep imports, which makes it unnecessary :-)
1 reply 0 retweets 3 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 