# \`conda-forge\` package

**URL:** <https://discourse.nodered.org/t/conda-forge-package/95684>\
**Category:** Core Development\
**Created:** [26 February 2025 20:18 UTC](https://discourse.nodered.org/t/conda-forge-package/95684 "2025-02-26T20:18:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![phreed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/phreed/32/95321_2.png) [@phreed](https://discourse.nodered.org/u/phreed)\
**Post date:** [26 February 2025 20:18 UTC](https://discourse.nodered.org/t/conda-forge-package/95684/1 "2025-02-26T20:18:42Z")

</div>

> <https://github.com/conda-forge/staged-recipes/pull/29292>
>
> Checklist
> \- \[x\] Title of this PR is meaningful: e.g. "Adding my\_nifty\_package",… not "updated meta.yaml".
> \- \[x\] License file is packaged (see \[here\](https://github.com/conda-forge/staged-recipes/blob/5eddbd7fc9d1502169089da06c3688d9759be978/recipes/example/meta.yaml#L64-L73) for an example).
> \- \[x\] Source is from official source.
> \- \[x\] Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
> \- \[x\] If static libraries are linked in, the license of the static library is packaged.
> \- \[x\] Package does not ship static libraries. If static libraries are needed, \[follow CFEP-18\](https://github.com/conda-forge/cfep/blob/main/cfep-18.md).
> \- \[x\] Build number is 0.
> \- \[x\] A tarball (\`url\`) rather than a repo (e.g. \`git\_url\`) is used in your recipe (see \[here\](https://conda-forge.org/docs/maintainer/adding\_pkgs.html#build-from-tarballs-not-repos) for more details).
> \- \[x\] GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
> \- \[x\] When in trouble, please check our \[knowledge base documentation\](https://conda-forge.org/docs/maintainer/knowledge\_base.html) before pinging a team.

I am in the process of making a conda package for node-red.  
There are a number of advantages to making npm packages available via conda.  
I am wondering if there is any interest in this by the node-red core developers?  
Thanks

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [26 February 2025 20:26 UTC](https://discourse.nodered.org/t/conda-forge-package/95684/2 "2025-02-26T20:26:58Z")

</div>

> [@phreed](#):
>
> There are a number of advantages to making npm packages available via conda.

Could you articulate those please?

---

<div class="post-metadata">

**Author:** ![phreed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/phreed/32/95321_2.png) [@phreed](https://discourse.nodered.org/u/phreed)\
**Post date:** [26 February 2025 21:39 UTC](https://discourse.nodered.org/t/conda-forge-package/95684/3 "2025-02-26T21:39:18Z")

</div>

There are several conda-forge clients, {conda, mamba, micromamba, pixi}.  
I mostly use [`pixi`](https://pixi.sh/latest/).  
The original `conda` is python only but `pixi` is written is rust and is cross platform,

- environment management: pnpm works in a similar way, but packages are installed into environments which can be: global-named, project specific, global-default
- multi-language: conda allowed for packages written in many languages.
- multi-os and multi-arch: due to its interpreted nature these are features of javascript but this is true for conda-forge packages regardless of language.
- binary packages: probably not directly relevant to node-red but prebuilt binaries are allowed in packages. This would be most useful for nodes used in flows which interact with other services written in non-javascript languages. For example, I am working on packaging flows which interacts with the [matrix.org](http://matrix.org) chat and another which interacts with mediamtx.
- [https://conda-forge.org/](https://conda-forge.org/)

Those are probably the main points.

To be clear, I am not proposing a replacement for the npm package for node-red.  
The conda-forge package uses the npm package to build its package.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [27 February 2025 01:04 UTC](https://discourse.nodered.org/t/conda-forge-package/95684/5 "2025-02-27T01:04:13Z")

</div>

Hi. I don’t have strong feelings either way. Must admit not heard of it until now (apart from for python of course). But yes feel free to create and promote it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [28 April 2025 01:04 UTC](https://discourse.nodered.org/t/conda-forge-package/95684/6 "2025-04-28T01:04:52Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.