Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Error in webpack build

Open
#212 2 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
babel, javascript, webpack
Domain
build-system

Research direction

The report points to a webpack import and stack frames in node_modules/babel-traverse/lib/path/index.js and lib/index.js. Start by reproducing the library import with webpack and confirm whether the JavaScript heap out-of-memory failure still occurs; done means the build completes without that error.

Written by the indexing model from the issue text.

Description

I'm having the following error return by including when importing the lib (using webpack)

<--- Last few GCs --->

[10376:0000021F7CCE6A80] 91373 ms: Mark-sweep 1403.6 (1471.6) -> 1403.6 (1471.6) MB, 3185.3 / > 0.0 ms allocation failure GC in old space requested
[10376:0000021F7CCE6A80] 94535 ms: Mark-sweep 1403.6 (1471.6) -> 1403.5 (1441.6) MB, 3162.2 / > 0.0 ms last resort gc
[10376:0000021F7CCE6A80] 98458 ms: Mark-sweep 1403.5 (1441.6) -> 1403.5 (1441.6) MB, 3922.3 / > 0.0 ms last resort gc

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 000003E47A5C0D59
1: get [C:...\node_modules\babel-traverse\lib\path\index.js:~76] > [pc=000003FB7F207CC0](this=00000398E240A6F1 <JS Function NodePath (SharedFunctionInfo > 0000031798DE04C1)>,_ref=00000181DD2CF4D1 <an Object with map 000001C7B096A2D1>) > 2: node [C:...\node_modules\babel-traverse\lib\index.js:~94] > [pc=000003FB7F1BBFC8](this=000002C01A19F381 <...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

Dominant language
JavaScript
Stars
13.7k
Forks
1.1k
PR merge metrics
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 sql-js/sql.js

All issues in sql-js/sql.js

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.