@notifi-network/notifi-node
Advanced tools
Comparing version 3.0.1 to 3.0.2-alpha.3
{ | ||
"name": "@notifi-network/notifi-node", | ||
"version": "3.0.1", | ||
"version": "3.0.2-alpha.3+13c4e3ab", | ||
"description": "Server-initiated operations with Notifi", | ||
@@ -27,3 +27,4 @@ "homepage": "https://github.com/notifi-network/notifi-sdk-ts#readme", | ||
"clean": "rimraf ./dist", | ||
"compile": "tsc -p tsconfig.build.json" | ||
"compile": "tsc -p tsconfig.build.json", | ||
"test": "jest" | ||
}, | ||
@@ -34,4 +35,4 @@ "bugs": { | ||
"dependencies": { | ||
"@notifi-network/notifi-dataplane": "^3.0.1", | ||
"@notifi-network/notifi-graphql": "^3.0.1", | ||
"@notifi-network/notifi-dataplane": "^3.0.2-alpha.3+13c4e3ab", | ||
"@notifi-network/notifi-graphql": "^3.0.2-alpha.3+13c4e3ab", | ||
"graphql": "^16.6.0", | ||
@@ -41,3 +42,7 @@ "graphql-request": "^6.0.0", | ||
}, | ||
"gitHead": "843cb0b40384295d6e7b3bfbd9fdb5c85aeb8383" | ||
"devDependencies": { | ||
"dotenv": "^16.4.5", | ||
"ethers": "^6.11.1" | ||
}, | ||
"gitHead": "13c4e3ab9adba415051b2b488f52f3412ee24f73" | ||
} |
@@ -245,4 +245,15 @@ # Notifi Node (@notifi-network/notifi-node) | ||
## Contributing & Testing | ||
We welcome and appreciate your contributions! Please review our [contribution guidelines](https://github.com/notifi-network/notifi-sdk-ts?tab=readme-ov-file#contribute-to-the-repository-for-contributors) before getting started. | ||
To ensure a smooth contribution process, please follow the steps below to confirm that all tests pass before submitting your changes: | ||
- Fill in the credentials in the `.env.example` file and rename it to `.env`. | ||
- Run `npm run test` to execute all tests. | ||
If your contribution includes a new feature, you may also want to create a dedicated test case within the` __tests__/NotifiNodeClient.test.ts` file to validate its functionality. | ||
## More example | ||
- [notifi-node-sample](): An example demonstrating how to use the `@notifi-network/notifi-node` package on express.js server. |
Manifest confusion
Supply chain riskThis package has inconsistent metadata. This could be malicious or caused by an error when publishing the package.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
36167
259
2
1
2