Skip to content

fix: downgrade p-limit from v5 to v4 for webpack compatibility#444

Merged
ruromero merged 1 commit intoguacsec:mainfrom
ruromero:fix/downgrade-p-limit-for-webpack
Mar 30, 2026
Merged

fix: downgrade p-limit from v5 to v4 for webpack compatibility#444
ruromero merged 1 commit intoguacsec:mainfrom
ruromero:fix/downgrade-p-limit-for-webpack

Conversation

@ruromero
Copy link
Copy Markdown
Collaborator

Summary

  • Downgrade p-limit from ^5.0.0 to ^4.0.0 to fix webpack bundling in downstream consumers

p-limit v5 uses Node.js subpath imports (#async_hooks) which webpack cannot resolve, causing:

Module not found: Error: Can't resolve '#async_hooks' in '.../node_modules/p-limit'

The API is identical between v4 and v5. The only v5 addition is AsyncResource wrapping for async context propagation (APM/tracing), which this project does not use.

Fixes #443

Test plan

  • Existing tests pass (npm test)
  • VS Code extension builds successfully with this version

🤖 Generated with Claude Code

p-limit v5 uses Node.js subpath imports (#async_hooks) which webpack
cannot resolve, breaking downstream consumers that bundle the client
(e.g., the VS Code extension). v4 has an identical API without the
subpath imports.

Fixes guacsec#443

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ruromero ruromero force-pushed the fix/downgrade-p-limit-for-webpack branch from a99cf1a to 01e9ee5 Compare March 30, 2026 07:43
@ruromero ruromero requested a review from Strum355 March 30, 2026 08:06
@ruromero ruromero merged commit b8af0f8 into guacsec:main Mar 30, 2026
4 checks passed
@ruromero ruromero deleted the fix/downgrade-p-limit-for-webpack branch March 30, 2026 08:20
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.

Downgrade p-limit from v5 to v4 for webpack compatibility

2 participants