[WIP] Refactor utilities ast file structure based on naming pattern

[Copilot]

Reorganize AST file structure following component naming pattern

Analysis Complete

• Analyze packages/core/src/component naming pattern
• Analyze current packages/utilities/ast/src structure
• Understand the import pattern (namespace imports won't break)
• Identify renaming strategy

Planned Changes

Following the pattern in packages/core/src/component where all files are prefixed with component-, the AST files should follow a consistent naming pattern with node- as the base prefix:

Files to rename:

• array-index.ts → node-array-index.ts
• array-method.ts → node-array-method.ts
• class-id.ts → node-class-id.ts
• expression-base.ts → node-expression-base.ts
• expression-is.ts → node-expression-is.ts
• expression-nested.ts → node-expression-nested.ts
• function-id.ts → node-function-id.ts
• function-init-path.ts → node-function-init-path.ts
• function-is.ts → node-function-is.ts
• property-name.ts → node-property-name.ts
• literal.ts → node-literal.ts
• misc.ts → node-misc.ts
• traverse.ts → node-traverse.ts
• process-env-node-env.ts → node-process-env-node-env.ts
• vitest-mock.ts → node-vitest-mock.ts

Files already following pattern (no changes):

• node-equal.ts
• node-format.ts
• node-is.ts
• node-selectors.ts
• node-types.ts

Implementation Steps

• Rename all files
• Update imports in the renamed files
• Update index.ts exports
• Update test files
• Run build and tests
• Verify no external imports are broken

Original prompt

根据 packages/core/src/component 下 file structure 的命名 pattern 重新梳理 packages/utilities/ast/src 下的 file structure

---

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
eslint-react	Ready	Preview, Comment	Dec 31, 2025 10:46am