tslib
tslib copied to clipboard
microsoft
Runtime library for TypeScript helpers.
This adds type information to the `__values(…)` and `__asyncValues(…)` helper functions. --- review?(@DanielRosenwasser)
This adds typed overloads to `__assign`, along with a **TSDoc** comment copied from `lib.es2015.core.d.ts#ObjectConstructor.assign(…)`. --- review?(@DanielRosenwasser)
**Babel** has been doing this since https://github.com/babel/babel/pull/10161, https://github.com/babel/babel/pull/10574 and https://github.com/babel/babel/pull/10585.
This adds a _tslib.cjs.js_ file as the package main to reduce the impact of global variable pollution, as well as some [additional variants](https://github.com/Microsoft/tslib/pull/52#issuecomment-388952872). Also, in an effort to avoid redundancy...
It was a _surprise_ for me I was using `tslib` indirectly, due to an dependency of another package. When I removed this package, the compilation ceased to build my solution...
We are seeing numerous packages which depend on tslib 1.x and 2.x. We'd like to de-duplicate these, but there doesn't seem to be clear docs on if it's safe to...
__spread ```js var tslib = require("tslib"); const { concat } = require('lodash') var testPushES6 = function(abc) { var arr1 = [1,2,3,-1] var arr2 = [4,5,6,7,8,9,10,12,13,14,15,16,17,18,29,30,31,32,33,34,35,36,37,38,39,40] const arr = arr1.push(...arr2) }...
This used to work before version 1.14.0 and is **still** listed in the README: ```js var tslib_1 = require("tslib"); exports.x = {}; exports.y = tslib_1.__assign({}, exports.x); ``` I consider this...
When upgrading to the newest versions of tslib, typescript, and jest I received the following error in an existing project: ``` TypeError: Cannot redefine property: upsertThing at Function.defineProperty () ```...
`__asyncGenerator` `__asyncValues` `__awaiter` These three helpers in *tslib* use the global `Promise` to create promises but in my project, I need tslib to use my implementation of the Promise compliant...
