Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [incubation] Publishing to npm and handling of CQs for npm/nodejs dependencies

Hi Thomas,

regarding the _javascript_ CQs: As you figured out, processing single CQs for _javascript_ can be a rather frustrating process. So I would encourage you, unless you see a real benefit, to create a single CQ for all your dependencies, and simply accept that _javascript_ dependencies are … well, I stop right here :)

From what I understand, you can release parts of your project with a different release Type. So core Ditto could remain Type B, while the "Ditto _javascript_ Client" could be release as Type A.

On Tue, Aug 27, 2019 at 9:35 AM Jaeckle Thomas (INST/ECS1) <thomas.jaeckle@xxxxxxxxxxxx> wrote:

Hi incubation list.


We, the Eclipse Ditto project [1], are currently working on an initial _javascript_ client [2] for our backend.

We would like to publish/release that to npm and are now wondering if there are processes/guides/best practices on how to publish modules to npm.


And, in addition: what is the process of creating CQs for npm dependencies we use in our client?

I saw some CQs which just provide their “package.json” along with all the sources of the dependencies from “node_modules” which npm creates, e.g. [3] or [4]

While that is a really simple way, when doing that we have no chance of reusing/piggybacking on already approved npm dependencies.

On the other side I see that it is really crazy how much transitive dependencies are pulled from some npm modules.


Also, all npm depdencies CQs I saw were “Type A” and our project is currently a “Type B” project and we would like to keep it that way.


Any advice/guidance or experience is much appreciated :-)









Mit freundlichen Grüßen / Best regards

Thomas Jaeckle

Engineering Cloud Services 1 Bosch IoT Things (INST/ECS1)
Bosch Software Innovations GmbH | Ziegelei 7 | 88090 Immenstaad | GERMANY

Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Michael Hahn, Dr. Aleksandar Mitrovic


incubation mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Jens Reimann
Principal Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
phone: +49 89 2050 71286

Red Hat GmbH,,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Tom Savage, Michael O'Neill

Back to the top