build: restructure for dual ESM/CJS output, update tooling, and enhance utilities

[dimaslanjaka]

check list

• Add test cases for the changes.
• Passed the CI test.

Description

Summary

This PR modernizes the build, testing, and linting infrastructure while introducing utility enhancements and ensuring compatibility with both ESM and CommonJS consumers.

Changes

• Build & Packaging

  • Updated package.json for ESM/CJS dual output with proper exports map
  • Cleaned up and simplified build scripts
  • Added .last_build marker to .gitignore for internal build tracking
  • Removed legacy tsconfig-split approach in favor of unified build process

• Linting & CI

  • Removed legacy .eslintrc.json and switched to eslint.config.mjs for native ESM lint configuration
  • Updated GitHub Actions linter workflow to build before linting
  • Changed lint script name to lint for consistency

• Testing

  • Updated .mocharc.yml to:
    • Use recursive test discovery (./test/**/*.spec.ts)
    • Limit to .ts extensions for clarity
  • Improved consistency for test file organization

• Repository Hygiene

  • Expanded .gitignore to include:
    • *.ignore, *.patch, *.diff, .vscode/, yarn.lock
    • Generated files like lib/highlight_alias.ts and .last_build
  • Changed highlight_alias.json ignore pattern to catch it in all subdirectories

• Utilities

  • feat(json): add support for circular JSON stringify/parse #430
  • feat(lib): implement custom deepMerge with recursion depth limit and circular reference support #429
  • feat(util): add cross-platform __dirname and __filename support for ESM #431
  • Updated README to document new utilities

Why

To align with modern Node.js packaging practices, ensure smooth compatibility across ESM and CJS consumers, streamline the build/test/lint process, and expand utility functionality.

Notes

• Build now produces consistent dual outputs with proper exports handling
• Tests and linting run in a more maintainable, ESM-friendly setup
• New JSON utilities simplify handling of circular structures

[SukkaW]

Not a fan of using rollup directly (hard to setup, needs to manually install many dependencies). Probably use bunchee instead?

[dimaslanjaka]

Not a fan of using rollup directly (hard to setup, needs to manually install many dependencies). Probably use bunchee instead?

can bunche target bundles to older node versions? like babel.
remembering hexo works from node 12.
or strict version of node to make unsupported for old node version?

[dimaslanjaka]

ok, now i change to default hybrid typesript compiler. without rollup. this also work on ESM, but sometimes need using babel to transform for htmlparser2 which isnt yet supported for ESM

[dimaslanjaka]

might need shim export for backward-compatibility import, this script will automate map export like older hexo-util.

file scripts/build_exports.mjs

import fs from 'fs';
import path from 'path';
import { fileURLToPath } from 'url';

const __filename = fileURLToPath(import.meta.url);
const __dirname = path.dirname(__filename);
const packageJsonPath = path.join(__dirname, '../package.json');
const packageJson = JSON.parse(fs.readFileSync(packageJsonPath, 'utf-8'));

const defaultExports = {
  '.': {
    'import': './dist/esm/index.js',
    'require': './dist/cjs/index.js',
    'types': './dist/esm/index.d.ts'
  },
  './highlight_alias.json': './highlight_alias.json',
  './dist/highlight_alias.json': './highlight_alias.json'
};

fs.readdirSync(path.join(__dirname, '../lib')).forEach(file => {
  defaultExports[`./dist/${file.replace('.ts', '')}`] = {
    'import': `./dist/esm/${file.replace('.ts', '.js')}`,
    'require': `./dist/cjs/${file.replace('.ts', '.js')}`,
    'types': `./dist/esm/${file.replace('.js', '.d.ts')}`
  };
});

// Sort the exports to ensure consistent output
const sortedExports = Object.keys(defaultExports).sort().reduce((obj, key) => {
  obj[key] = defaultExports[key];
  return obj;
}, {});

packageJson.exports = sortedExports;

fs.writeFileSync(packageJsonPath, JSON.stringify(packageJson, null, 2) + '\n', 'utf-8');

sample result at dimaslanjaka/hexo-util

[coveralls]

coverage: 73.017% (-23.9%) from 96.875%
when pulling bfaacfd on dimaslanjaka:esm-shim
into d497bc7 on hexojs:master.

[D-Sketon]

The PR is too large; splitting it into smaller ones might be better.

[D-Sketon]

Not a fan of using rollup directly (hard to setup, needs to manually install many dependencies). Probably use bunchee instead?

can bunche target bundles to older node versions? like babel.
remembering hexo works from node 12.
or strict version of node to make unsupported for old node version?

The next major version of Hexo will drop Node 18. Given this, do we still need Babel?

[dimaslanjaka]

The PR is too large; splitting it into smaller ones might be better.

because supporting both ESM and CJS, we need refactor all codebases like (import with extension, drop require, pollyfil __dirname, refactor tests for mocha suitable with ESM environment, etc)

[dimaslanjaka]

The next major version of Hexo will drop Node 18. Given this, do we still need Babel?

emm no need babel, but when still support ESM and CJS, still need for bundle typescript to both environment safely without rewriting codebase for ESM and CJS independently.

[dimaslanjaka]

@D-Sketon another approach without editing too much codebase to supporting esm and cjs

• test unit using jest which has built-in transformer
• bundler using rollup (without babel when targeting node 20+ just using plugin json,commonjs,module resolver)
  but @SukkaW not a fan of rollup bundler. so, editing all codebases too ESM and CJS independently is the solution.

when using tsup, need .cjs patch to fix ESM compiled file imported under cjs compiled file (like this PR do)

[dimaslanjaka]

dissapointed