EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Lobsters·7d ago·5 min read
Friendship ended with Deno, now Node is my best friend
TL;DR
After a long period of using Deno, the author returns to Node.js for a SvelteKit project and finds significant improvements in its APIs and ECMAScript support. The transition highlights the author's preference for modern tooling and stability in client projects.
✦ Why It Matters
Consider switching to Fast Node Manager and PNPM for better version control and security in your Node.js projects.
Key Takeaways
- Explore the latest features in Node.js for modern development.
- Use Fast Node Manager for efficient Node version management.
- Adopt PNPM to enhance security against malware in dependencies.
- Create aliases for scripts to streamline your development workflow.
Full Summary
The author, previously a Deno user, has switched back to Node.js while working on a SvelteKit client project. They express surprise at the advancements in Node.js, noting that many outdated APIs have been modernized and that ECMAScript features are now well-supported.
The author mentions the official Node documentation's recommendation to use NVM (Node Version Manager) for managing Node.js and NPM (Node Package Manager), but shares a preference for Fast Node Manager (FNM) due to past issues with NVM. To enhance security, they opted for PNPM, a package manager that mitigates risks associated with malware in NPM.
The author also created aliases for scripts that require specific binary names, showcasing a practical approach to managing dependencies in their projects.