upstash-redis
publint
upstash-redis | publint | |
---|---|---|
2 | 6 | |
616 | 892 | |
3.6% | - | |
7.9 | 8.3 | |
about 10 hours ago | 5 days ago | |
TypeScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
upstash-redis
-
Creating an NPM Package in 2024 (Deno, dnt)
upstash
-
Wrangler and environment variables issue with Workers
other redis wrangler.toml but it seems they commented it out.
publint
- TypeScript NPM Packages Done Right
-
Creating an NPM Package in 2024 (Deno, dnt)
Creating npm packages can be challenging. We've seen many tools in this domain, and I encourage you to try dnt. With dnt, I was finally able to pass the package.json linter, which is no small achievement (try jotai, redux, vite).
- Publint: NPM Package Publication Linter
-
AreTheTypesWrong with Andrew Branch from the TypeScript Team
Only regret is not mentioning https://publint.dev which is similar in many ways (and also great -> just didn't know about it at the time). Maybe we gotta find the publint people/person and do an episode with them??
-
The Javascript Ecosystem for the Dazed and Confused
There are many quirks related to this however, for example if you use "types" it should always be the first entry in your exports, and if you use "default" it should always be the last entry in your exports. Package exports are easy to mess up, and get wrong. Thankfully, there's a really nice project called publint that helps you with things like these.
-
A new linter to check if a package is published right
Not currently, but missing deps is planned under https://github.com/bluwy/publint/issues/13 which should be doable once the infrastructure is done. Deprecated dependencies are probably out of scope for now as that package could technically still work, and it avoids a fetch to npm.
What are some alternatives?
socket.io-redis - Adapter to enable broadcasting of events to multiple separate socket.io server nodes.
openai-node - The official Node.js / Typescript library for the OpenAI API
node-redis - A high-performance Node.js Redis client. [Moved to: https://github.com/redis/node-redis]
esm-env
node-redis - Redis Node.js client
SimpleWebAuthn - WebAuthn, Simplified. A collection of TypeScript-first libraries for simpler WebAuthn integration. Supports modern browsers, Node, Deno, and more.
1Backend - Run your web apps easily with a complete platform that you can install on any server. Build composable microservices and lambdas.
is-bun - Return true if you are running in Bun.
upstash-kafka - HTTP based Kafka Client for Serverless and Edge Functions
is-not-bun - Return true if you are running not in Bun.
stepci - Automated API Testing and Quality Assurance