The Node Protocol plugin was incorrectly handling modules that require the node: prefix and modules that already have the prefix. This caused two main issues:

1. Double prefixing: When nodeProtocol: true was used, modules that already had the node: prefix would get another prefix added, resulting in node:node:path instead of node:path.

2. Stripping required prefixes: When nodeProtocol: 'strip' was used, modules that REQUIRE the node: prefix (like node:test, node:sqlite, node:sea, node:test/reporters) would have their prefix stripped, making them invalid.

Example of the problem:

// Before fix - with nodeProtocol: true
import fs from 'fs'
import { join } from 'node:path'
// Would output: import fs from "node:fs"; import { join } from "node:node:path";

// Before fix - with nodeProtocol: 'strip'  
import test from 'node:test'
import sqlite from 'node:sqlite'
// Would output: import test from "test"; import sqlite from "sqlite"; (invalid!)

Solution:

• For adding mode (nodeProtocol: true): Check if modules already have the node: prefix and preserve them as-is instead of adding another prefix.

• **For stripping mode (nodeProtocol: 'strip')**: Identify modules that require the node: prefix (node:sea, node:sqlite, node:test, node:test/reporters`) and preserve their prefix even in strip mode.

After fix:

// With nodeProtocol: true
import fs from 'fs'
import { join } from 'node:path'
// Correctly outputs: import fs from "node:fs"; import { join } from "node:path";

// With nodeProtocol: 'strip'
import test from 'node:test'
import sqlite from 'node:sqlite'  
// Correctly outputs: import test from "node:test"; import sqlite from "node:sqlite";

The fix includes comprehensive test cases to validate both scenarios and maintains backward compatibility with existing functionality.

Fixes #482.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.