Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

wrong "authorOrganization" NodeProject field type

See original GitHub issue

HI, I’m afraid the NodeProject authorOrganization field type, now boolean, should be string instead.

(thank you for your amazing work!)

Issue Analytics

State:
Created a year ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

Chriscbrcommented, Jun 14, 2022

@fabio-vitali-docebo @tompahoward I was able to found the source! It’s an additional field used by jsii: https://aws.github.io/jsii/user-guides/lib-author/configuration/

Closing this out since I think the mystery is solved 😃

0reactions

tompahowardcommented, Jun 14, 2022

From what I can find, I can’t tell author.organziation should be a field in the package.json, let alone if it should be a string or boolean. @fabio-vitali-docebo do you have a reference that says it should be a string?

author is a Maintainer https://github.com/npm/types/blob/master/index.d.ts#L17 And a Maintainer has a name, email and url https://github.com/npm/types/blob/master/index.d.ts#L17 No mention of an organization field.

The docs at https://docs.npmjs.com/cli/v8/configuring-npm/package-json#people-fields-author-contributors don’t mention an organization field either.

From what I can see, author.organization was added in https://github.com/projen/projen/commit/e773a0dcab0ace15cabca4db8dbc95924248e7ad

@eladb, sorry I’m no expert here, can you help us find where author.organization comes from? Is it an old field that’s no longer in the npm code/docs or is it an extension that other tools use? TIA