esm-bundle / chai Goto Github PK

View Code? Open in Web Editor NEW

1.0 1.0 4.0 987 KB

BDD / TDD assertion framework for node.js and the browser that can be paired with any testing framework.

License: MIT License

JavaScript 97.88% Shell 2.12%

chai's People

Contributors

Stargazers

Watchers

Forkers

mgenware larsdenbakker whjvenyl rictic

chai's Issues

Deprecate package on NPM

Please deprecate the package on NPM and guide users to use the regular chai package, which supports ESM since 4.3.0. This will help prevent users from installing this package, thinking that they need it to run chai in an ESM environment.

Is this repo still needed?

I'm cleaning up esm-bundle projects so they are easier to maintain and migrating them off travis-ci.

Is this project/repo still needed? How is it being used right now?

npm package is outdated

The npm package hasn't been updated in over a year. Chai is now at 4.3.7 and this package is published as 4.3.4-fix.0 (which, as #280 mentions, is a weird version in and of itself).

Update failure 4.3.1

I am using this repo in my project

"chai": "npm:@esm-bundle/chai@^4.3.0"

Running npm run update fails with this error message:

git:(master) npm update

> @esm-bundle/[email protected] postinstall src_path/node_modules/chai
> husky install

sh: husky: command not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! @esm-bundle/[email protected] postinstall: `husky install`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the @esm-bundle/[email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

TS import error

When importing the library the TS says it cannot be resolved. However, the tests are run as expected.

The error message I see is:

Unable to resolve path to module '@esm-bundle/chai'. eslint(import/no-unresolved)

I am not sure why is this happening. Possibly it's a wrong path to the d.ts file?

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

Update dependency @types/chai to v4.3.11

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Update dependency chai to v4.4.1
Update dependency chai to v5
Update dependency rollup to v4
Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/build-and-test.yml

actions/checkout v4@b4ffde65f46336ab88eb53be808477a3936bae11

actions/setup-node v4

pnpm/action-setup v3.0.0

actions/checkout v4@b4ffde65f46336ab88eb53be808477a3936bae11

actions/setup-node v4

pnpm/action-setup v3.0.0

npm

package.json

@types/chai ^4.2.12

@rollup/plugin-commonjs 25.0.7

@rollup/plugin-node-resolve 15.2.3

chai 4.3.4

concurrently 8.2.2

husky 9.0.11

karma 6.4.2

karma-firefox-launcher 2.1.2

karma-jasmine 5.1.0

mocha 10.3.0

pinst 3.0.0

prettier 3.2.5

pretty-quick 4.0.0

release-it 17.1.1

release-it-plugin-esm-bundle 3.0.0

rollup 2.79.1

rollup-plugin-terser 7.0.2

nvm

.nvmrc

Check this box to trigger a request for Renovate to run again on this repository

Publish failure 4.3.5

It seems that the 4.3.5 has not been correctly published to npm.

See https://github.com/esm-bundle/chai/actions/runs/826320941

Latest tag on npm is 4.3.4-fix.0

The latest-tagged version of @esm-bundle/chai on npm is 4.3.4-fix.0. Is this intentional? What's a bit weird about that is that any x.y.z-* suffix has lower precedence than x.y.z, which means currently the latest tag is behind the highest semver version. The -fix suffix implies it might be an amendment, though. In that case, I think 4.3.5 should be published.