Ulrich Stark comments

Results 27 comments of


                                            Ulrich Stark

[Deps] remove object.assign

I think it's time to drop Node 4 support to remove the object.assign dependency. What's the reason for still supporting Node 4?

[Deps] remove object.assign

The reasons to remove dependencies are simple, well known and also apply to this proposed change: - reduce installation size/time - reduce fragmentation of packages - easier maintainability - less...

[Deps] remove object.assign

Thanks for the work you do first of all. Your packages are widely used by many popular packages maintained by you and others. This is my last attempt to align...

Remove string-prototype-matchall

@surma Could you please merge this and publish a new version? This unnecessary dependency would significantly unbloat the dependency tree. Thanks in advance for your time!

Make `AstKind` consistent

#11535 is my attempt to do this for all jsx types.

Make `AstKind` consistent

#11597 creates AstKinds for all jsdoc types

Make `AstKind` consistent

#11617 removes ForStatementInit from AstKind

Make `AstKind` consistent

> If anyone would like to try getting rid of AstKind::ArrayExpressionElement, that'd be a big help. Done in #11684

Non-idempotent and incorrect placement of line comments in between property accessors

The input code is extracted from the function `getClassNameFromPrototypeMethod` in https://github.com/microsoft/TypeScript/blob/11e79327598db412a161616849041487673fadab/src/compiler/checker.ts

[BUG] `npm update` generates package-lock.json that isn't considered in-sync by `npm ci`

> I guess this is a duplicate of [#8669](https://github.com/npm/cli/issues/8669) I'm not sure. My issue is also present in 11.6.0 while your linked issue seems to have appeared first in 11.6.2.