npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, πŸ‘‹, I’m Ryan HefnerΒ  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you πŸ™

Β© 2026 – Pkg Stats / Ryan Hefner

mulle-environment-editor

v0.0.11

Published

πŸ•οΈ GUI Editor for the mulle-sde environment

Readme

Mulle Environment Editor

A visual editor for mulle-sde environment files.

screeny

Features

  • Visual Environment Editing: Edit environment variables in a clean, modern interface
  • Scope Management: Manage different environment scopes (project, global, host-specific, user-specific, etc.)
  • Loading Order: Drag-and-drop interface to reorder environment loading priority
  • Real-time Preview: See how your environment variables will be applied
  • Recent Projects: Quick access to recently opened projects
  • Cross-platform: Works on Linux, macOS, and Windows

Installation

From Source

# Clone the repository
git clone https://github.com/mulle-sde/mulle-environment-editor.git
cd mulle-environment-editor

# Install dependencies
npm install

# Run the application
npm start

Local Installation

To install the CLI globally for local development:

# From the project directory
npm link

# Now you can run from anywhere
mulle-environment-editor

To uninstall:

npm unlink -g mulle-environment-editor

Pre-built Binaries

Download the latest release for your platform from the releases page.

Usage

  1. Open a Project: Launch the application and click "Open Project" to select a directory containing a .mulle folder
  2. Select Environment Scope: Choose from available scopes in the sidebar (project, global, host-specific, etc.)
  3. Edit Variables:
    • Add new variables with the "Add Variable" button
    • Edit variable names, values, and comments inline
    • Toggle variable enablement with checkboxes
    • Remove variables with the delete button
  4. Reorder Loading Priority: Drag and drop scopes in the loading order section
  5. Save Changes: Click "Save" to write changes back to the environment files

Loading the Environment into Your Shell

This is the job mulle-sde and mulle-env do for you automatically. But you can do this also manually.

After editing environment files, you need to source them to apply the changes to your shell:

# Source the environment into your current shell
cd /path/to/your/project
. .mulle/share/env/environment.sh

This will load all environment variables according to their priority and scope applicability.

Testing Environment Without Affecting Your Shell

To preview what environment variables will be set without modifying your current shell:

# Run in a clean environment and display all variables
env -i bash -c '. .mulle/share/env/environment.sh && env | sort'

# Or export from the editor and test the exported script
env -i bash -c '. environment-export.sh && env | sort'

The env -i command starts with an empty environment, so you can see exactly what the environment files set up.

Environment File Structure

The editor works with mulle-env environment file structure:

.mulle/etc/env/           # Local environment files
β”œβ”€β”€ environment-project.sh
β”œβ”€β”€ environment-global.sh
β”œβ”€β”€ environment-host-*.sh
β”œβ”€β”€ environment-user-*.sh
β”œβ”€β”€ environment-os-*.sh
└── auxscope              # Loading order configuration

.mulle/share/env/         # Shared environment files
β”œβ”€β”€ environment-extension.sh
β”œβ”€β”€ environment-plugin.sh
└── environment.sh

License

MIT License - see LICENSE file for details.

footer