Skip to main content

Changing Names of our Node Packages

· 3 min read
Stefan Benicke
Stefan Benicke
Senior Developer @ Eyeson

We're excited to announce that we've updated how we publish our Node.js packages: going forward, all our packages will be published under the @eyeson organization scope on npm.

What's Changing?​

Previously, our packages were named like this:

  • eyeson
  • eyeson-node

Now, they'll be published like this:

  • @eyeson/js
  • @eyeson/node

This change only affects the package names — all functionality remains the same, and you can continue using our libraries as usual with a small update to your package.json.

Deprecation Notice

The old packages (e.g. eyeson-node) will remain available until July 1st, 2025. After that date, they will no longer receive updates and may be removed from npm entirely.

Why We're Making This Change​

We made this update for a few important reasons — all of which benefit you as much as they do us:

  • Better Clarity and Trust
    Scoped packages make it immediately clear that a package comes from our team. It adds confidence, especially when working with multiple dependencies.

  • Easier Maintenance and Discovery
    All our packages are now grouped under the @eyeson scope, making it easier to discover and manage them as a set — whether you're browsing npm or searching within your project.

  • Reduced Risk of Name Conflicts
    Scoped naming helps avoid accidental conflicts with similarly named public packages, providing a safer and more predictable developer experience.

  • Streamlined Permissions and Security
    Using npm organizations allows us to better manage access, publishing rights, and versioning — which translates to more reliable and secure packages for you.

Deprecation Notice: Old Package Names​

To make this transition smooth for everyone:

  • The old packages (e.g. eyeson-node) will remain available until July 1st, 2025.
  • After that date, they will no longer receive updates and may be removed from npm entirely.

We strongly encourage you to migrate to the new scoped packages before that deadline.

What You Need to Do​

If you’re using one of our packages, simply update the package name in your package.json.

For example:

Before:
"dependencies": {
  "eyeson-node": "^1.4.0"
}
After:
"dependencies": {
  "@eyeson/node": "^1.4.0"
}
  • eyeson => @eyeson/js
  • eyeson-node => @eyeson/node
  • eyeson-node-layer => @eyeson/node-layer
  • eyeson-node-svg-layer => @eyeson/node-svg-layer

Then run your usual install command:

npm install
# or
yarn install
# or
pnpm install

Thanks for Your Support​

We're committed to improving your experience as a developer and believe this change will lead to a cleaner, safer, and more scalable ecosystem for everyone using our tools.

If you have any questions or run into issues during the transition, don't hesitate to reach out to us!