You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Stefan Seifert <ss...@pro-vision.de> on 2019/09/05 13:55:59 UTC

[hackathon] Sling Packager / npm tooling

- up to now we have no sling module that ends up in the npm registry - the sling packager is the first one
- we need to clarify the technical details how to deploy the npm package on npm registry
- an organization in NPM should be used, e.g. "apache-sling"
- ci testing could be done by adding a maven pom in the sling package which setups a sling test instance and executes the npm integration tests from maven (using one of the available maven nodejs plugins)
- publishing releases in npm registry has to be done manually (until we find a way to automate it in the CI)
- how do wie manage credentials for the npm registry?
- probably we should use the existing process for maven releases and staging in the Apache Nexus for npm projects as well for release and voting process - and then add an additional publish step to the NPM registry
  - will it then additionally end up in the maven repository?
- probably we should look at the apache openwhisk project - they have lot of npm releases, how do they do it?

stefan


Re: [hackathon] Sling Packager / npm tooling

Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,

On Thu, Sep 5, 2019 at 3:56 PM Stefan Seifert <ss...@pro-vision.de> wrote:
> ...- probably we should look at the apache openwhisk project - they have lot of npm releases, how do they do it?...

I haven't looked at the details so far but
https://github.com/apache/openwhisk-client-js is published on npm,
https://www.npmjs.com/package/openwhisk

-Bertrand

Re: [hackathon] Sling Packager / npm tooling

Posted by Robert Munteanu <ro...@apache.org>.
On Thu, 2019-09-05 at 13:55 +0000, Stefan Seifert wrote:
> - an organization in NPM should be used, e.g. "apache-sling"

I have asked infra for guidance (users@infra.apache.org is private
though, can't link back ). I think apache-sling/$module is a good
pattern to use, as we might want to keep the door open to multiple npm
packages.

Thanks,
Robert