Notice: Making a `conda-forge` package for `node-red`

General
1

I am making a conda-forge package for node-red.
If you would like to be a maintainer for the eventual feedstock,
make a comment on the PR conda-forge/staged-recipes#29292
indicating you would like to be included and I will make the update.
Thanks

2

Hello,

Just copy & pasting the same message you put in the issue is not useful here, please answer the questions I included:

explain what this is and why it will be of benefit to the project and why it should be owned by the project.

3

Using conda-forge for projects provides cross platform packages.
When used with pixi packages can be managed by project.
In my case, I need to be able to deploy node-red on raspberry-pi on different OS (fedora & ubuntu & piOS) at different versions (meaning different versions of nodejs) without worrying about compatibility with the host OS (a conda package lives in a conda environment, which is the important parts of the environment relative parts of the OS).
Can this be done with containers? Yes, partly, containers are great for applications but they struggle with library management. I often put a pixi (conda) environment in container.
I have no problem being the only maintainer of the node-red feedstock.
I thought it was rude to not at least invite you all.
Here are the references to better understand the conda-forge ecosystem including rattler-build and pixi.

You know how node-red has flows that wrap other applications and libraries,
and often libraries are written in non-javascript languages?
Conda lets you package those flows and their dependencies (a node-red flow package which depends on a library package).

4

Here is what an AI said on the subject:

Why use conda-forge?

  • Community-driven and comprehensive:
    conda-forge is a community-maintained channel for Conda, providing a vast collection of packages for various languages and scientific computing. It often offers more up-to-date versions and specialized packages compared to the default Conda channels.
  • Cross-platform and binary packages:
    Conda packages, including those from conda-forge, are typically pre-compiled binaries, ensuring consistent installations across different operating systems and architectures without requiring local compilation.
  • Dependency resolution:
    Conda's robust dependency solver handles complex interdependencies between packages, preventing conflicts and ensuring a stable environment.

Why use pixi?

  • Project-centric approach:
    pixi builds upon the Conda ecosystem but shifts focus from isolated environments to a project-based workflow. This allows for better organization and management of dependencies within a specific project.
  • Unified package management:
    pixi can manage packages from both the Conda ecosystem (including conda-forge) and PyPI, providing a single tool for handling dependencies from different sources.
  • Reproducible environments:
    pixi aims to create highly reproducible environments, ensuring that your project runs consistently across different machines and over time.
  • Enhanced features:
    pixi offers features beyond basic package management, such as task management, caching, and hardware-aware environment configurations, making it a more comprehensive tool for development workflows.

In summary:

conda-forge provides the broad and well-maintained package ecosystem, while pixi offers a modern, project-centric interface to manage these packages efficiently, alongside PyPI packages, in a highly reproducible and streamlined manner. This combination is particularly beneficial for data science, machine learning, and other scientific computing projects that often involve diverse dependencies and require robust environment management.