#npm

[bendita9-6]

Stephanie Lauter

The queen of Slaughter, Stephanie Lauter

[petrapixel]

here's a list of all the intermediate coding tutorials i've written so far!

git / github tutorial

npm (and node.js) tutorial (+ how to use the command line) (this one's a prerequisite for the following 2 tutorials)

webpack tutorial (a module builder for JavaScript and (S)CSS)

11ty (eleventy) tutorial (a super easy static site generator!)

if you have ideas/requests, feel free to contact me!

more beginner coding tutorials are coming VERY soon! meanwhile, check out my common questions and common mistakes pages!

[cyber-sec]

Hijacked npm Package Lets Hackers Run Code on Your System

Attackers slipped malicious code into the npm package is, downloaded millions of times weekly, giving them a live remote shell on developers’ machines. Linked to a wider phishing campaign, this attack shows why unchecked updates can be disastrous.

Source: Socket

Read more: CyberSecBrief

[fujocoded]

Funding FujoCoded: Stretch Goals!

It’s time! With our first goal met (🎉 thank you!), let’s talk about stretch goals. We have quite a few planned, so we're going to go through them one by one and explain what they are and why we chose them!

Before we go down the list, here's something fun:

Sticker Unlock: At 45 backers, we also unlocked one more sticker!

The goal of our campaign is to cover business expenses most of all. The unlocked content is an extra token of gratitude for your support that also helps us meet our own targets! 

With that said, let's get to our stretch goals...

$4,000: "That's Why I Ship On Company Time" Ao3 Sticker

At $4,000 we'll unlock one more sticker design that you can add to your collection! 

Our first version of this "shipping" sticker features VSCode and a terminal, but there's more than one type of shipping... here's to the other one!

$5,000: "Using NPM with Javascript" Article

Next up, we have our first article. Our plan is to add an Articles section to @fujowebdev where we'll collect simple, free guides to help beginners get past the roadblocks we see them encounter!

This first one will cover the basics of NPM, a core element of modern JavaScript!

"How do I install this JavaScript library? How do I run this open source JavaScript project? How can I get started creating my blog using a tool like @astrodotbuild?" are some of the most common questions we get in our Fandom Coders server. 

Let's give *everyone* the answer!

$6,000: Offering Website Art Prints

Next up, we'll turn the excellent art on our website into prints! These will be (probably) 8x10-sized art prints that will look amazing without breaking the bank. Full specs soon!

...and speaking of the site, you have tried moving the windows, right?

$7,000: "Catching Up With Terminal" Article

Next, another common issue for beginner developers: how to start learning how to handle the Terminal.

This will require some research to determine the major roadblocks, which is how our project operates: active learning from those going through it all!

$8,000: "Crucial Confrontations" Article

And last (for now), something very dear to us: an article extracting some wisdom from the book "Crucial Confrontations": https://www.amazon.com/Crucial-Confrontations-Resolving-Promises-Expectations/dp/0071446524

This may seem like an unusual choice, but it highlights how our teaching goals go beyond programming to cover collaboration!

After years of working within our community, we repeatedly found that developing effective communication and confrontation skills helps our collaborators thrive. Unfortunately, the world doesn't teach us how to effectively (but kindly) hold each other accountable.

Some of our most involved collaborators have read this book and found the tools within it transformative. Given this experience, we deeply believe that making some of this wisdom easily accessible (without having to read the full book) will allow all of us to collaborate better!

If we can reach $8,000, this will enable us to test this hypothesis and learn how teaching soft skills beyond programming influences what we're able to achieve! It's a bold idea, but we're excited to see how it turns out in practice.

Help us make it there!

And that's all...for now!

If you want to hop on Twitch right now, you can join us as we put some extra polish on our shiny new FujoCoded website.

And remember, you can back our campaign here to help us achieve these goals and more:

[cobwebinthecorner]

okay but seriously does Will Branner have an OnlyFans? asking for a friend

[soggedboytroutanti]

shoutout to jesus (@williamsewerratted) for inventing brookeschitz btw

[sammy0panda]

deno been real quiet

👀👀 i haven't tried this node.js/npm replacement called Bun yet, but on paper it seems neat :)

[stxalq]

is anything truly first-party? even the hardcore homelab folks still need a static ip and a reliable dns from a third-party

plus, these days, all critical js libraries start life hosted on third-party cdns. those daily/weekly metrics on their npm pages are download stats, not vibe checks

unless you're going to rebuild decades of web application infrastructure from scratch, apply all your security patches by hand, and rewrite every framework from zero, it's unavoidable, there's third-party cdns in your build and deployment pipelines. it's just a matter of who you trust, what risks you're willing to take, and what effort you're able to put in

I think the real reason most websites are janky as hell to use these days is because web developers have become so specialised that nobody really understands how anything works anymore. The other day I had to explain why hosting critical Javascript libraries on a third-party CDN is a bad idea to a "lead developer" who genuinely didn't know the difference between server-side versus client-side scripting.

[flux443]

AI-generated malicious npm package targets Solana wallets. Drains crypto from 1,500 users before being taken down.

A newly discovered, AI-generated malicious npm package targeting Solana wallet users has resulted in significant cryptocurrency losses before it was taken down, exposing serious vulnerabilities in the software supply chain. Here’s a detailed overview of the incident and its broader implications. Incident Overview Cybersecurity researchers have identified a sophisticated malicious package…

[atikinverse]

🚨 Day 59 of 100 Innovations!

Introducing: Atikin AutoDoc 🚀 Say goodbye to boring documentation! Atikin AutoDoc automatically generates crystal-clear, developer-friendly docs with code snippets, diagrams, and real examples — so your code speaks for itself. 💻📚

🔧 Built for devs. 🧠 Powered by Atikin Verse. 📦 Now on npm – atikin-autodoc 👉 Try it. Use it. Document smarter.

[nubecolectiva]

List of Axios Methods ! 🇺🇸 🔎Zoom: https://nubecolectiva.com/comunidad/flyers/axios-methods-list/

Lista de Métodos de Axios ! 🇪🇸 🔎Zoom: https://nubecolectiva.com/comunidad/flyers/lista-metodos-axios/

[iamdevbox]

Decoding JWT Tokens in JavaScript with jwt-decode

JSON Web Tokens (JWT) are a popular method for securely transmitting information between clients and servers. They're widely used in modern web applications, especially those built with React, Angular, or Vue.js. When working with JWT, you'll often need to decode them to extract the user's data. This is where the jwt-decode package comes in. To get started, install the jwt-decode package using npm or yarn: `npm install jsonwebtoken` or `yarn add jsonwebtoken`. Then, import the package in your JavaScript file and use the `decode()` function to decode your JWT. Here's a simple example: ``` const jwt = require('jsonwebtoken'); const token = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaGFuIjoiMjMwfQ.SflKxwRJSMeKKF2qt4FN9q74thSjsoLHMhbA6vrUxoo'; const decoded = jwt.decode(token); console.log(decoded); ``` This will output the decoded JWT data as a JavaScript object. Read more: Decoding JWT Tokens in JavaScript with jwt-decode

[cyber-sec]

North Korea Just Dropped 67 Malicious npm Packages

A North Korean hacking group is back with a new malware loader, XORIndex, and 67 fresh npm packages — already downloaded over 17,000 times — that exfiltrate your data and launch multi-stage malware targeting developers.

Source: Socket

Read more: CyberSecBrief

[kevinmarville]

Sync.io is a good website where you can learn new things with high precision

Run npm init -y to create a package.json file. Note: If you cloned the example repository, you won’t need to do this step.

[w2gsolution01]

Deno 2.3 Introduces Support for Local NPM Packages: A Game-Changer for JavaScript Developers

Deno 2.3 introduces support for local NPM packages, marking a significant milestone for developers working with JavaScript and TypeScript. This latest update to the modern runtime brings a host of enhancements that streamline workflows, boost performance, and deepen integration with the NPM ecosystem. For developers seeking a secure, efficient, and flexible environment, this release opens new doors for local package management and beyond. Let’s explore what makes this update a must-know for the JavaScript community.

Why Deno 2.3 Matters for Developers

The release of Deno 2.3 is more than just a version bump. It addresses key pain points for developers, particularly those working in complex projects that rely on NPM dependencies. By introducing support for local NPM packages, Deno empowers developers to test and iterate on modules without needing to publish them to a registry. This feature alone saves time and enhances the development experience, especially for those managing private or experimental packages.

Beyond local package support, the update includes improvements to compilation, code formatting, and observability. These additions make Deno an even stronger alternative to traditional runtimes like Node.js, offering a zero-config, secure-by-default environment that aligns with modern web standards.

The Power of Local NPM Package Support

One of the standout features of Deno 2.3 is its ability to handle local NPM packages seamlessly. Previously, developers had to publish packages to a registry or rely on workarounds to test locally. Now, Deno allows you to reference a local folder directly, making it easier to develop and debug NPM modules without external dependencies.

This feature is particularly valuable for teams working on monorepos or private libraries. By configuring a local node_modules directory, developers can ensure that their projects remain self-contained and reproducible. Whether you’re prototyping a new feature or refining an existing package, this capability reduces friction and accelerates iteration.

How Local NPM Support Enhances Workflows

Local NPM package support in Deno 2.3 introduces support for local NPM packages by allowing developers to specify a local path in their configuration files. This eliminates the need for constant publishing and republishing during development. For example, teams can now link a local package to multiple projects, test changes in real-time, and maintain control over their dependencies.

Additionally, Deno’s secure-by-default model ensures that local packages adhere to the same permission-based access controls as remote ones. This means you can experiment with local modules without compromising the integrity of your project. The result is a smoother, safer, and more efficient development process.

Enhanced Compilation Capabilities

Deno 2.3 doesn’t stop at package management. The update significantly improves the deno compile command, enabling developers to create standalone binaries with greater flexibility. These binaries now support Foreign Function Interface (FFI) and Node native add-ons, allowing for deeper integration with native libraries and plugins.

Building Leaner Binaries

A key enhancement to compilation is the ability to exclude specific files from the final binary. This feature lets developers reduce the size of their executables, making them more efficient for distribution. For instance, you can exclude development or test files, ensuring that only production-ready code is packaged.

The introduction of the Deno.build.standalone boolean flag further enhances compilation. This flag allows your code to detect whether it’s running in a compiled binary, enabling dynamic behavior based on the execution context. Whether you’re toggling features or customizing error messages, this introspective capability adds a layer of sophistication to your applications.

Cross-Platform Compatibility

With Deno 2.3, compiled binaries are more versatile than ever. The support for FFI and Node add-ons means you can leverage platform-specific libraries without sacrificing portability. This makes Deno an attractive choice for building cross-platform tools, from command-line utilities to desktop applications.

Improved Code Formatting with deno fmt

Code consistency is critical for collaborative projects, and Deno 2.3 delivers with an upgraded deno fmt command. This formatter now supports embedded CSS, HTML, and SQL within tagged templates, ensuring that your mixed-content codebases remain tidy and readable.

New Formatting Options

The update introduces 14 new formatting options, giving developers fine-grained control over their code’s appearance. Whether you’re working with JavaScript, TypeScript, or embedded languages, these options let you tailor formatting to your team’s preferences. This is a boon for projects with diverse file types, as it reduces the need for external formatters.

Streamlined CI Pipelines

Deno 2.3 also extends the --permit-no-files flag to deno fmt and deno lint. This prevents errors when no files are found, making it easier to integrate formatting and linting into continuous integration (CI) pipelines. By reducing false positives, this enhancement saves time and ensures smoother automation.

Boosted Observability with OpenTelemetry

Observability is a cornerstone of modern application development, and Deno 2.3 strengthens its OpenTelemetry support. This update adds event recording, span context propagation, and V8 engine metrics, giving developers deeper insights into their applications’ performance.

Monitoring Made Simple

With expanded OpenTelemetry features, you can capture detailed telemetry data and export it to tools like Grafana or Honeycomb. This makes it easier to diagnose bottlenecks, track user interactions, and optimize resource usage. For teams running production workloads, these capabilities are invaluable for maintaining reliability.

Seamless Integration

Deno’s OpenTelemetry support integrates seamlessly with existing observability stacks. Whether you’re monitoring a serverless function or a full-fledged API, the added metrics and tracing options provide a comprehensive view of your application’s behavior. This aligns with Deno’s goal of simplifying complex workflows without sacrificing power.

Performance and Ecosystem Improvements

Deno 2.3 brings a slew of performance optimizations, particularly for projects with NPM dependencies. Package installation via deno install and deno add is now up to twice as fast when dependencies are cached. This speed boost is especially noticeable in large monorepos, where redundant dependency resolution has been minimized.

Upgraded Engines

The update includes upgrades to TypeScript 5.8 and V8 13.5, bringing new language features and performance improvements. These enhancements ensure that Deno remains at the cutting edge of JavaScript and TypeScript development, offering developers the latest tools to build robust applications.

Better Jupyter Integration

For data scientists and researchers, Deno 2.3 improves the Jupyter notebook experience. Variables, modules, and type definitions are now shared across cells, making it easier to explore datasets and prototype scripts. This enhancement positions Deno as a compelling choice for interactive JavaScript and TypeScript development.

Why Choose Deno 2.3?

Deno 2.3 introduces support for local NPM packages, but its impact goes far beyond this single feature. With improved compilation, formatting, observability, and performance, this release solidifies Deno’s position as a modern, developer-friendly runtime. Its seamless integration with the NPM ecosystem, combined with a secure and zero-config approach, makes it an ideal choice for both new and existing projects.

Whether you’re building a startup’s backend, a personal CLI tool, or a data visualization dashboard, Deno 2.3 offers the tools you need to succeed. Its focus on simplicity, security, and performance ensures that you can focus on writing code rather than wrestling with configuration.

Getting Started with Deno 2.3

Ready to dive into Deno 2.3? Getting started is straightforward. If you haven’t installed Deno yet, you can do so with a single command from the official website. Once installed, explore the new features by creating a project and experimenting with local NPM packages or compilation.

The Deno documentation provides detailed guides on leveraging local package support, formatting options, and observability features. For community support, check out the Deno subreddit or GitHub repository, where developers share tips and discuss the latest updates.

Deno 2.3 introduces support for local NPM packages, delivering a feature that developers have long awaited. Combined with enhanced compilation, improved formatting, and robust observability, this release makes Deno a powerhouse for JavaScript and TypeScript development. By addressing real-world needs with practical solutions, Deno 2.3 empowers developers to build faster, safer, and more maintainable applications.