Gathering detailed insights and metrics for inversify-hooks-esm
Gathering detailed insights and metrics for inversify-hooks-esm
npm install inversify-hooks-esm
Typescript
Module System
Min. Node Version
Node Version
NPM Version
67.4
Supply Chain
96.4
Quality
75.4
Maintenance
100
Vulnerability
100
License
TypeScript (100%)
Verify real, reachable, and deliverable emails with instant MX records, SMTP checks, and disposable email detection.
Total Downloads
1,982
Last Day
3
Last Week
12
Last Month
53
Last Year
424
MIT License
5 Commits
2 Watchers
2 Branches
1 Contributors
Updated on Aug 29, 2021
Minified
Minified + Gzipped
Latest Version
2.1.2
Package Id
inversify-hooks-esm@2.1.2
Unpacked Size
21.26 kB
Size
5.57 kB
File Count
11
NPM Version
9.6.6
Node Version
18.16.0
Published on
May 12, 2023
Cumulative downloads
Total Downloads
Last Day
200%
3
Compared to previous day
Last Week
1,100%
12
Compared to previous week
Last Month
29.3%
53
Compared to previous month
Last Year
-20.9%
424
Compared to previous year
4
31
Congrats! You just saved yourself hours of work by bootstrapping this project with TSDX. Let’s get you oriented with what’s here and how to use it.
This TSDX setup is meant for developing libraries (not apps!) that can be published to NPM. If you’re looking to build a Node app, you could use
ts-node-dev
, plaints-node
, or simpletsc
.
If you’re new to TypeScript, checkout this handy cheatsheet
TSDX scaffolds your new library inside /src
.
To run TSDX, use:
1npm start # or yarn start
This builds to /dist
and runs the project in watch mode so any edits you save inside src
causes a rebuild to /dist
.
To do a one-off build, use npm run build
or yarn build
.
To run tests, use npm test
or yarn test
.
Code quality is set up for you with prettier
, husky
, and lint-staged
. Adjust the respective fields in package.json
accordingly.
Jest tests are set up to run with npm test
or yarn test
.
size-limit
is set up to calculate the real cost of your library with npm run size
and visualize the bundle with npm run analyze
.
This is the folder structure we set up for you:
1/src 2 index.tsx # EDIT THIS 3/test 4 blah.test.tsx # EDIT THIS 5.gitignore 6package.json 7README.md # EDIT THIS 8tsconfig.json
TSDX uses Rollup as a bundler and generates multiple rollup configs for various module formats and build settings. See Optimizations for details.
tsconfig.json
is set up to interpret dom
and esnext
types, as well as react
for jsx
. Adjust according to your needs.
Two actions are added by default:
main
which installs deps w/ cache, lints, tests, and builds on all pushes against a Node and OS matrixsize
which comments cost comparison of your library on every pull request using size-limit
Please see the main tsdx
optimizations docs. In particular, know that you can take advantage of development-only optimizations:
1// ./types/index.d.ts 2declare var __DEV__: boolean; 3 4// inside your code... 5if (__DEV__) { 6 console.log('foo'); 7}
You can also choose to install and use invariant and warning functions.
CJS, ESModules, and UMD module formats are supported.
The appropriate paths are configured in package.json
and dist/index.js
accordingly. Please report if any issues are found.
Per Palmer Group guidelines, always use named exports. Code split inside your React app instead of your React library.
There are many ways to ship styles, including with CSS-in-JS. TSDX has no opinion on this, configure how you like.
For vanilla CSS, you can include it at the root directory and add it to the files
section in your package.json
, so that it can be imported separately by your users and run through their bundler's loader.
We recommend using np.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 0/4 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
48 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-03-10
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More