Brett Zamir

I'm not the maintainer, but it seems, as you can see in visiting the URLs in question, that you are using a registry which requires authentication. If you use the...

@delfrrr : Are you still maintaining? Do you want a collaborator to be able to make updates? I'm pretty busy, but would like to get those PRs merged and what...

I think the problem is in `getLicenseType`. Trying "GPL-3.0-or-later OR MIT" gives "protective". while "GPL-3.0-or-later OR Artistic-2.0" gives "permissive".

And the source of that problem is that in `satisfies`, `spdx-correct` is used on the "GPL-3.0-or-later OR MIT" argument, giving "GPL-3.0", and `upgrade: false` is not used as it can...

As the author has not replied and seems to have abandoned the project, I created a fork, `npm-reflect` which should address this issue (try v1.0.0) as well as some others...

> But in well-formed doc comments, the `*` framing always has a space after it. Is this TSDoc specific? Because in JSDoc, there is no such stated requirement except that...

Yeah, I agree with the discussion, which in summary essentially seems to be: ```js /** * @yields {IndividualTypeYielded} i.e., `yield value;` * @next {TypePassedInWithIteratorNextCall} I.e., `it.next(SomeObject)` * @returns {ResultThatWillAccompanyIteratorDone} i.e.,...

@octogonz: I was indicating that for just these reasons: 1. To quickly summarize what type of type it was 2. To indicate the pattern that regular jsdoc would use.

Before giving specific specs, might it be viable to allow an alternative to `@returns {Generator}` which could define a new global template such as: `@returns {GeneratorFunction}`. While this would still...

> The goal of `@babel/parser` to parse ECMAScript and its proposal, as well as some popular extension such as TypeScript / Flow. However, JSDoc does not fall into this catalogue:...