Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Legacy builds are not included in NPM package.

See original GitHub issue

New legacy builds were added in #215 to support older versions of Node etc, but it appears that the legacy built files are missing in the published NPM package for v0.4.1: https://unpkg.com/browse/colorjs.io@0.4.1/dist/

I’m not sure what the build/release process is for colorjs.io, but when I npm pack locally the files are included correctly – perhaps npm run build wasn’t run before the new release? In case that’s the issue, I’ll open a PR to address that with a prepack script.

Issue Analytics

State:
Created a year ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

LeaVeroucommented, Nov 1, 2022

One downside of using v0.4.1-patch.1 is that it’s not installed by either ^0.4.1 or even ^0.4.1-patch.1, and can only be installed with 0.4.1-patch.1 directly. But that’s probably best practice for a pre-1.0 dependency anyway, so 🤷

Ah, I didn’t know that. Even more reason to implement alpha blending and release it in 0.4.2!

1reaction

jgerigmeyercommented, Nov 1, 2022

This seems to be fixed for me in v0.4.1-patch.1. ~~I’m not sure why it’s not working on unpkg, but maybe that’s an issue on their end?~~ It’s available now on unpkg: https://unpkg.com/browse/colorjs.io@0.4.1-patch.1/dist/

One downside of using v0.4.1-patch.1 is that it’s not installed by either ^0.4.1 or even ^0.4.1-patch.1, and can only be installed with 0.4.1-patch.1 directly. But that’s probably best practice for a pre-1.0 dependency anyway, so 🤷

Top Results From Across the Web

What does npm install --legacy-peer-deps do exactly? When ...

--legacy-peer-deps does not roll back any dependencies to any version. It simply just doesn't try to install peer dependencies automatically. – ...

package.json - npm Docs

Files included with the "package.json#files" field cannot be excluded through .npmignore or .gitignore . Certain files are always included, regardless of ...

[BUG] npm ci can't resolve dependencies without --force, or ...

An easy way to do this is to run, for example, npm config set legacy-peer-deps=true --location=project and commit the .npmrc file to your...

Best practices for publishing your npm package - mikbry

I mainly use Rollup bundler to build a legacy package with support for ESM ... Some files or directories should be excluded. ......

Building for production - Lit.dev

This configuration is suitable for serving to modern browsers that can run ES2019 JS without polyfills. Required node modules: npm i --save-dev rollup...