npm package not published?

[ahmadnassri]

there is a package.json with a package name: oas-schemas but this package doesn't exist in npmjs.com ...

[MikeRalphson]

This is WIP.

There is some discussion on PR #1911

Note that publishing to npm will make the schemas available via the unpkg CDN too for non-JS use-cases.

The TODO list which used to be on that PR, I have now copied here:

• confirm TSC group email to use for npm author property (or none?)
• determine if Apache-2.0 LICENSE file also needs including in generated packages (resolved by @kylef)
• which npm org to publish packages to (new/existing)? - A Michael Adams (this one?) has used oai but has no published packages
• package naming
• who will have publish rights (i.e.who owns the npm login to provide the auth token?) We don't want to introduce any technical steps with a "bus factor" of one
• versioning of generated packages on schema changes
• setup automated publishing via Travis GitHub Actions deploy
• deprecate swagger-schema-official package - @mohsen1 ?
• close related issues Make schema an npm/bower module and publish is independently  #137 Host schema publicly #151

[ahmadnassri]

excellent, thanks for the update!

[MikeRalphson]

which npm org to publish packages to (new/existing)? - A Michael Adams (this one?) has used oai but has no published packages

I've been in contact with D. Michael Adams of the Ocean Assets Institute (OAI!) and he is willing to transfer the npm org to us, but npm themselves are not currently doing this until they draft a new process. We could use oas instead (which I have reserved).