Skip to content

chore: upgrade @apexdevtools/apex-parser to v5#742

Draft
lukecotter wants to merge 1 commit intocertinia:mainfrom
lukecotter:chore-apex-parser-v5
Draft

chore: upgrade @apexdevtools/apex-parser to v5#742
lukecotter wants to merge 1 commit intocertinia:mainfrom
lukecotter:chore-apex-parser-v5

Conversation

@lukecotter
Copy link
Contributor

Summary

  • Upgrade @apexdevtools/apex-parser from v4 to v5 in both lana and log-viewer
  • Fix browser build by adding stubApexParserCheck() plugin to rollup (matching rolldown) — stubs Check.js which unconditionally imports node:fs/node:path
  • Remove unnecessary antlr4 aliases from both build configs — bundlers resolve the correct entry via package.json exports conditions (node/browser)
  • Add exportConditions: ['node'] to rollup's nodeResolve for proper Node.js export resolution
  • Update SOQL parser/linter and Apex visitor/symbol locator for v5 API changes

Test plan

  • pnpm build — no unresolved dependency warnings
  • pnpm test — all 720 tests pass
  • pnpm lint — clean
  • Manual: load extension in VS Code, open DB view, confirm no node:fs CORS errors

- Upgrade apex-parser from v4 to v5 in lana and log-viewer
- Add stubApexParserCheck() plugin to both rollup and rolldown configs
  to stub Check.js (which imports node:fs/node:path) for browser builds
- Remove unnecessary antlr4 aliases — bundlers resolve the correct
  entry point via package.json exports conditions
- Add exportConditions: ['node'] to rollup lana build for proper
  Node.js export resolution
- Update SOQL parser/linter and Apex visitor/symbol locator for v5 API

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant