GitShow/Rich-Harris/estree-walker
Rich-Harris

estree-walker

Traverse an ESTree-compliant AST

by Rich-Harris
Star on GitHubForknpm

JavaScript

423 stars36 forks12 contributorsQuiet · 9mo agoSince 2015MIT

Meet the team

See all 12 on GitHub →
Rich-Harris
Rich-Harris80 contributions
kristoferbaxter
kristoferbaxter11 contributions
ChristianMurphy
ChristianMurphy5 contributions
Conduitry
Conduitry4 contributions
mrkishi
mrkishi4 contributions
tanhauhau
tanhauhau3 contributions
AndrewLeedham
AndrewLeedham1 contribution
benmccann
benmccann1 contribution

Languages

View on GitHub →
JavaScript100%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

2 of 6 standards met

Community profile →
42
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Quiet · 4 in progress · Last activity 9mo ago
See all on GitHub →
samwightt
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in... errorOpenIssue

Getting an error when I try to use estree-walker with esbuild: Node Version: v14.15.4 tsconfig.json:

samwightt · 1y ago
jacobbogers
sourcemapsOpenIssue

Would it be possible to automatically generate sourcemap when rendering the output?

jacobbogers · 1y ago
tanhauhau
Add main to work around eslint-plugin-importOpenPR
tanhauhau · 1y ago

Recent fixes

View closed PRs →
jrTilak
fix: add CommonJS export to estree-walker package.json to resolve ERR…MergedPR

…_PACKAGE_PATH_NOT_EXPORTED error fixes #26 The error ERR_PACKAGE_PATH_NOT_EXPORTED occurs because the estree-walker package does not have an appropriate export defined for CommonJS modules in its package.json file. By adding to the exports field, you explicitly define the entry point for CommonJS modules, which resolves the issue.

jrTilak · 1mo ago
cernymatej
feat: add support for calling `leave` when skipping a nodeMergedPR

resolves https://github.com/Rich-Harris/estree-walker/issues/41 It can be useful to skip a node while walking an AST, yet still invoke the callback for cleanup logic. In Nuxt, for example, we use alongside a scope tracker that requires the callback to be triggered in order to track the scopes properly. This PR adds the ability to skip a node while still calling the callback. I'm open to suggestions regarding the API. I was also considering making it call by default, but that would obviously be a breaking change. Should we go in that direction, or keep the current behavior as the default? Should I add this functionality for node removal as well? I can imagine the situation might be similar.

cernymatej · 7mo ago
Structured data for AI agents

Repository: Rich-Harris/estree-walker. Description: Traverse an ESTree-compliant AST Stars: 423, Forks: 36. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Open PRs: 4, open issues: 5. Last activity: 9mo ago. Community health: 42%. Top contributors: Rich-Harris, kristoferbaxter, ChristianMurphy, Conduitry, mrkishi, tanhauhau, AndrewLeedham, benmccann, TrySound, forivall and others.

·@ofershap

Replace github.com with gitshow.dev