Configure @dportillo-ixs/htmldocs for npm publication and apply Windows path fix

[Copilot]

Fork configuration to publish as @dportillo-ixs/htmldocs on npmjs.org, plus backport of Windows path fix from upstream PR #18.

Changes

• Windows path fix: Add escapeForRegExp function to escape special regex characters in file paths before passing to esbuild's RegExp filter. Fixes Windows backslash handling.

export function escapeForRegExp(s: string): string {
  return String(s).replace(/[-\/\\^$*+?.()|[\]{}]/g, "\\$&");
}

// Usage in plugin
const escapedPaths = documentTemplates.map(escapeForRegExp);
b.onLoad({ filter: new RegExp(escapedPaths.join("|")) }, ...);

• Package rename: htmldocs → @dportillo-ixs/htmldocs in packages/htmldocs/package.json

• npm registry config: Update root package.json publishConfig to use registry.npmjs.org with access: public

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• fonts.googleapis.com
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/htmldocs/htmldocs/packages/htmldocs/node_modules/.bin/../next/dist/bin/next build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Objective

Configure the htmldocs package to be published as @dportillo-ixs/htmldocs on npmjs.org and apply the Windows path fix from the upstream PR #18.

Background

This fork of htmldocs-js/htmldocs is being created to maintain an active version of the package since the original repository is no longer maintained. There is an important fix in PR #18 (htmldocs-js#18) that resolves Windows path issues with esbuild that needs to be applied.

Changes Required

1. Apply Windows Path Fix (from PR #18)

The PR #18 by jorgefl8 (commit SHA: 9c0ad14) fixes issue #17:

• Adds an escapeForRegExp function to safely escape special regex characters
• Fixes issue where Windows paths with backslashes caused esbuild to fail
• Ensures compatibility with esbuild's Go/RE2 regex engine
• Modifies 1 file with 14 additions and 1 deletion

You need to identify which file was changed in the esbuild plugin configuration and apply similar changes to:

• Add a function to escape regex special characters
• Use this function to escape Windows paths before using them in regex filters

2. Change Package Name

In packages/htmldocs/package.json:

• Change "name": "htmldocs" to "name": "@dportillo-ixs/htmldocs"

3. Configure npm Publication

In the root package.json:

• Change the publishConfig section from:

  "publishConfig": {
    "registry": "https://npm.pkg.github.com"
  }

  To:

  "publishConfig": {
    "registry": "https://registry.npmjs.org",
    "access": "public"
  }

Expected Outcome

After these changes:

1. The package will be ready to publish as @dportillo-ixs/htmldocs on npmjs.org
2. The Windows path issue will be resolved
3. Users can install with: npm install @dportillo-ixs/htmldocs
4. The GitHub Actions workflow will automatically publish to npm when merged to main

Notes

• The NPM_TOKEN secret is already configured in the repository
• The existing release workflow should work once these changes are merged to main
• This creates a maintained fork with critical bug fixes applied

This pull request was created as a result of the following prompt from Copilot chat.

Objective

Configure the htmldocs package to be published as @dportillo-ixs/htmldocs on npmjs.org and apply the Windows path fix from the upstream PR #18.

Background

This fork of htmldocs-js/htmldocs is being created to maintain an active version of the package since the original repository is no longer maintained. There is an important fix in PR #18 (htmldocs-js#18) that resolves Windows path issues with esbuild that needs to be applied.

Changes Required

1. Apply Windows Path Fix (from PR #18)

The PR #18 by jorgefl8 (commit SHA: 9c0ad14) fixes issue #17:

• Adds an escapeForRegExp function to safely escape special regex characters
• Fixes issue where Windows paths with backslashes caused esbuild to fail
• Ensures compatibility with esbuild's Go/RE2 regex engine
• Modifies 1 file with 14 additions and 1 deletion

You need to identify which file was changed in the esbuild plugin configuration and apply similar changes to:

• Add a function to escape regex special characters
• Use this function to escape Windows paths before using them in regex filters

2. Change Package Name

In packages/htmldocs/package.json:

• Change "name": "htmldocs" to "name": "@dportillo-ixs/htmldocs"

3. Configure npm Publication

In the root package.json:

• Change the publishConfig section from:

  "publishConfig": {
    "registry": "https://npm.pkg.github.com"
  }

  To:

  "publishConfig": {
    "registry": "https://registry.npmjs.org",
    "access": "public"
  }

Expected Outcome

After these changes:

1. The package will be ready to publish as @dportillo-ixs/htmldocs on npmjs.org
2. The Windows path issue will be resolved
3. Users can install with: npm install @dportillo-ixs/htmldocs
4. The GitHub Actions workflow will automatically publish to npm when merged to main

Notes

• The NPM_TOKEN secret is already configured in the repository
• The existing release workflow should work once these changes are merged to main
• This creates a maintained fork with critical bug fixes applied

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.