openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <>
Subject Re: Changing JavaScript SDK NPM Module Name: openwhisk => apache-openwhisk?
Date Mon, 15 Jul 2019 17:05:24 GMT
The name with the dash looks nicer, agreed. In migrating from an old
package name to a new one where you already have existing users, I
haven't seen a solution to that myself quite yet, though I know that
Groovy has a similar problem where their packages are still published
under the `org.codehaus.groovy` group id instead of
`org.apache.groovy`. While Maven and NPM are quite different, the
method of migrating a package name is similarly not well-defined in
both systems.

Does anyone have more info about how NPM runs their repository? Maybe
they can add in some redirects of some sort.

On Mon, 15 Jul 2019 at 11:11, James Thomas <> wrote:
> Reviewing the ASF guidelines on NPM packages to check our JS SDK satifises
> all the rules[1] - we're supposed to be publishing the NPM package as
> "apacheopenwhisk" and not "openwhisk". This NPM library was published at (
> before the project was donated to
> Apache.
> Moving from the library to publish at `apache-openwhisk` rather than
> `openwhisk`[2] is not technically challenging (and the new package name is
> available) but will cause numerous issues....
> I'm asking for comments on what to do about this. Would like to engage the
> ASF mentors for advice as well. What does the community think about this?
> The library has significant usage (NPM tells me the library is averaging 6k
> downloads a week) using the existing package name. GitHub lists 38K
> references to the module.
> All those external dependent projects, blog posts, documentation and
> tutorials, etc, that reference the library (and are outside of our control)
> will be reliant on the old package name. These will still work (as the old
> library version will still be available from NPM) but never receive new
> versions on installing the dependency. This may eventually mean the old
> library doesn't work with future platform changes and/or lead to security
> issues with outdated dependencies.
> I'm not sure if there's any leeway in the allowing the short-name for the
> NPM library (given we follow all the other requirements)? This will be a
> significant amount of work just changing all the references in project we
> control.
> If we do change the name - I'd assume `apache-openwhisk` is fine. Using
> `apacheopenwhisk` is slightly horrid....
> [1] -
> [2] - following NPM JS module conventions - apache-openwhisk is much
> preferable than a single word (apacheopenwhisk).
> --
> Regards,
> James Thomas

Matt Sicker <>

View raw message