You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can probably help with some use cases for "Cases for bundledPackageName in 4.2"
Decentraland used this feature to create libraries. Our runtime supports AMD, like VSCode. And our environment works with the stupidest build process ever: we concatenate AMD files. No webpack, rollup or any other transformation needed.
We also leverage Typescript to do the task of compiling the AMD and also to enable the proper typing of the imports.
The problem this flag solved may be very specific but it made us remove (a ton) of dependencies to analyze the code and post-process it. .d.ts is easy, even regex works. generated .js was very difficult in comparision.
Imagine a library exposing an index file.
It used to generate a code like this
define("index", ....)
And that's ok. Until you need another library, with a file named index.
define("index",..lib1..)define("index",..lib2..)
This flag enabled the compilers to prepend the name of the lib to both the generated code and the .d.ts
Origin Types for Unions
#36392
Foo: Foo
becauseFoo
is in scope..d.ts
emit or quick info..types
files won't display what a user sees..types
baselines, we might be doing the wrong thing for.d.ts
emit.Capture
Constructor.prototype
in Emit#33363
Yadda.prototype
.Yadda_prototype
, minifiers can compact those into something likex
..prototype
Destructuring Patterns in
for
-in
Loops#33337
downlevelIteration
?__read
helper that could do this.Allow Non-
super
Non-this
Code in Derived classes beforesuper()
#29374
super()
.Cases for
bundledPackageName
in 4.2#41499
The text was updated successfully, but these errors were encountered: