• Replace CommonJS require.resolve with path.resolve for WASM file resolution
• Improve webpack compatibility by using explicit path resolution
• Remove unnecessary createRequire import and usage

Replace require.resolve with path.resolve for WASM loading

• Replace createRequire from 'node:module' with path import
• Change WASM file resolution from require.resolve() to path.resolve(__dirname, ...)
• Improve webpack compatibility by using explicit file path resolution
• Simplify module initialization by removing CommonJS require wrapper

src/providers/requirements_parser.js

Description

init() now calls Language.load(path.resolve(__dirname, ...)) in an ESM module, which can throw
ReferenceError: __dirname is not defined and prevents requirements.txt parsing from working. This
failure propagates to the pip provider because it calls getParser() during analysis.

Code

src/providers/requirements_parser.js[7]

+	return await Language.load(path.resolve(__dirname, 'tree-sitter-requirements', 'tree-sitter-requirements.wasm'));

Evidence

The package is ESM (type: module + TS emits module: esnext), so __dirname is not reliably
available; the codebase itself already guards __dirname usage elsewhere via try/catch. The pip
provider imports and executes getParser() (which calls init()), so any requirements.txt analysis
will hit the failing WASM load path.

src/providers/requirements_parser.js[1-12]
package.json[23-36]
tsconfig.json[1-25]
src/index.js[68-83]
src/providers/python_pip.js[10-15]
src/providers/python_pip.js[98-103]
src/provider.js[15-27]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`src/providers/requirements_parser.js` resolves the Tree-sitter WASM using `path.resolve(__dirname, ...)`. In this repo the package is ESM (`type: module`, TS emits `module: esnext`), so `__dirname` is not reliably available and the WASM resolution will fail, breaking requirements parsing.

### Issue Context
- `python_pip` and `python_controller` call `getParser()` which calls `init()` and thus executes the failing `Language.load(...)` path.
- The repo already contains an ESM-safe pattern for directory resolution in `src/index.js`.

### Fix Focus Areas
- src/providers/requirements_parser.js[1-12]

### Implementation direction
Update `init()` to resolve the WASM in an ESM-safe way:
- Preferred for Node runtime correctness: restore `createRequire(import.meta.url)` and `require.resolve('tree-sitter-requirements/tree-sitter-requirements.wasm')`.
- Alternative (Node ESM): use `import.meta.resolve('tree-sitter-requirements/tree-sitter-requirements.wasm')` and convert `file://` URL to a filesystem path before calling `Language.load`.
- If the intent is to load a WASM you ship within *this* package: add a build/prepack copy step to place the WASM under `dist/...` and derive the module directory via `fileURLToPath(new URL('.', import.meta.url))` (do not use `__dirname`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools