HTML MASTER CLASS /// LEARN TAGS /// BUILD STRUCTURE /// SEMANTIC WEB /// HTML MASTER CLASS /// LEARN TAGS ///

Untitled Lesson

⚡ Total XP: 0|💻 backend XP: 0

Skill Matrix

UNLOCK NODES BY LEARNING NEW TAGS.

Select an unlocked node to view details root

Pascual Vila

Full-Stack Software and AI Engineer

Full-Stack Software and AI Engineer with 6 years of experience building enterprise-grade web applications across React, Angular, Node.js, and Python. Recently completed a Master's in AI Development specializing in LLMs, RAG, and AI agent architectures, and currently builds enterprise systems that integrate AI and Digital Twins to optimize industrial and logistics processes.

LinkedIn ↗

Common Pitfalls & Errors

The Error //

Assuming every Node built-in module has a legacy bare-specifier alias

// Wrong — throws, no bare alias exists
import { test } from "test";

// Correct — the only valid form
import { test } from "node:test";

The Solution //

Modules introduced after the node: convention was established — like node:test and node:sqlite — are only accessible via the prefixed form and have no bare "test" or "sqlite" alias at all. Attempting a bare import for these throws a module-not-found error, not a warning.

The Error //

Inconsistently mixing prefixed and bare imports across a codebase with no linting enforcement

// .eslintrc — enforces the convention automatically
{ "rules": { "unicorn/prefer-node-protocol": "error" } }

The Solution //

Without a lint rule enforcing one convention, a codebase drifts into a mix of "fs" and "node:fs" imports depending on which developer or era wrote each file — harmless functionally, but it undermines the readability benefit of being able to instantly distinguish core imports from third-party ones at a glance.