TypeScript VS lodash

TypeScript公式サイト

There's also a slight performance caveat when it comes to interfaces vs intersections (&) to keep in mind: https://github.com/microsoft/Typescript/wiki/Performance#pre...

Tip: You can find official docs and guides at typescriptlang. org.

Node.js and TypeScript installed locally

Language: TypeScript (for type safety and better developer tooling)

It's extremely popular in React, Node.js, and full-stack TypeScript applications because it provides:

https://github.com/microsoft/TypeScript/blob/main/LICENSE.tx...

The license is Apache 2.0. With the trademark, they can tell everyone not to call their thing TypeScript but at this point, given the license, they cant't tell them not to copy it and change it and distribute that new thing (assuming the new distributors do so under the correct conditions).

TypeScript

}

But that is not the case, so you’d need a single cast to make it work (from number to ClampedNumber<1,200>) or however exactly you’d want to express this.

Tbf having looked more closely into how typescript handles number range types, I don’t think I would ever use them. Not very expressive or clear. I think I hallucinated something closer to what is in this proposal: https://github.com/microsoft/TypeScript/issues/43505

I still think that the general idea of communicating what acceptable input is via the type system is a good one. But the specifics of doing that with numbers isn’t great in typescript yet.

A hypothetical but likely scale would be from typo/docs fixes (lowest), bugfixes, new features, to CI/CD and release workflow (highest). Generally, the wider audience your patch might influence, the more you are expected to know about the project itself, its workflow, collaboration, best practices, code quality and maturity, etc. in the first place.

I agree that banning people without prior communication is rude, but looking at OP's PR[^1], I tend to concur with lodash maintainers this time. The PR gets no description, no explanation, and no prior discussion or RFCs. It adds a totally new GitHub Actions pipeline, while lodash isn't even using GitHub Actions now. It contains various fixup commits that should be squashed. One commit has a super long subject that should be split up. OP here went straight to the top level to propose a brand new release workflow, but the lodash maintainers obviously didn't consider them to be ready for such contributions.

These are common mistakes every contributor would make in the beginning, and I don't think the maintainers meant it personal. As many other comments have pointed out, by choosing an easier task, getting familiar with the workflow, and building trust, OP can get their patch landed.

[^0]: https://www.mozilla.org/en-US/about/governance/policies/comm...

[^1]: https://github.com/lodash/lodash/pull/6014

> Perhaps Google and Mozilla, leaders in JavaScript standards and implementations, will start developing a real standard library for JavaScript, which makes micro-dependencies like left-pad a thing of the past. This could be combined with a consolidation of efforts, merging micro-libraries into larger packages with a more coherent and holistic scope and purpose, which prune their own dependency trees in turn.

Sorry but this is as big as a strawman as possible. Both of these "solutions that won't happen" are already happening:

- The ECMAScript standard already defines a `Strong.padStart()` as part of the bigger standard library of Javascript [1]

- There is very well known a larger package that combines many micro-utilities like this into one, lodash [2]

[1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

[2] https://lodash.com/

I would probably look at the lodash implementation (for JS/TS) as a complete implementation example.

https://github.com/lodash/lodash/blob/8a26eb42adb303f4adc7ef...

Lodash: A utility library that offers easy-to-use debounce and throttle functions.

lodash

Here's an example. This is the PR they created in lodash's GitHub repo:

https://github.com/lodash/lodash/pull/5980

Lodash is a popular JavaScript utility library that provides a convenient debounce function. It's a straightforward approach if you're already using Lodash in your project.

The _.merge function from Lodash is a powerful utility for deep merging. It recursively merges nested properties from source objects into a target object.

To help us understand this system, VSCode offers a command "Developer: Inspect Editor Tokens and Scopes" that displays a tooltip with information about the currently selected code. Here's an example with the compact function from Lodash: