v3.0.9 Bug: Can't resolve 'fs'

Open
#389 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, typescript
Domain
frontend, web-dev

Research direction

Compare the v3.0.9 and v3.0.1 package entry points and dependency behavior, focusing on where the client-side build reaches the Node-only 'fs' package. Reproduce the failure in a browser-based application, then verify that the generated client-side bundle works without requiring 'fs' while Node usage remains functional.

Written by the indexing model from the issue text.

Description

v3.0.9 it no longer works on client-side applications. It now relies on the 'fs' package which is only available in node (and not, for example, the browser). This was not the case on v3.0.1. Please fix.

Dominant language
TypeScript
Stars
1.2k
Forks
242
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Kong/httpsnippet

All issues in Kong/httpsnippet

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.