dp
dp
PostsComments
PD🧩 Plasmo Developers
Created by dp on 4/1/2024 in #👾extension
plasmo dev is failing
@lab any hints? Thank you
7 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
Yes it seems our build was keeping node_modules and creating some nested node_modules that was enlarging the directory before zipping.
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
But we'l try to reduce it
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
100mb I believe
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
@lab
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
Ok we just zip it using zip and it worked
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
If you'd like to analyze your bundle, you can use the --bundle-buddy flag, combined with --source-maps to generate a Bundle Buddy Just read it ; nice
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
I see the plasmo build CLI just call parcel -- but we can't pass much options to parcel such as yarn build --reporter @parcel/reporter-bundle-analyzer https://github.com/PlasmoHQ/plasmo/blob/main/cli/plasmo/src/commands/build.ts#L38 WOuld it be possible to pass parcel functions?
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
It seems the build node_modules directory include typescript, parcel... and lot of things (sass, react-dev-tools) ; probably we need to move to dev dependencies
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
Ok it seems our build dir is 402mb; compressed manually with zip makes it 114mb. I will look why this is aas big as that
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
Ha nice; let me see
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
Yes it's not exiting and keep going on Github Runner -- Need to stop the job manually 
🟡 19     | Creating BGSW entry
🟡 20     | Hash changed, updating manifest
#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0x7c4f096fdcc0
----- Native stack trace -----
<--- Last few GCs --->
<--- JS stacktrace --->
#
# Fatal javascript OOM in MemoryChunk allocation failed during deserialization.
#
<--- Last few GCs --->
<--- JS stacktrace --->
FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
<--- Last few GCs --->
<--- JS stacktrace --->
#
# Fatal javascript OOM in MemoryChunk allocation failed during deserialization.
#
🟡 19     | Creating BGSW entry
🟡 20     | Hash changed, updating manifest
#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0x7c4f096fdcc0
----- Native stack trace -----
<--- Last few GCs --->
<--- JS stacktrace --->
#
# Fatal javascript OOM in MemoryChunk allocation failed during deserialization.
#
<--- Last few GCs --->
<--- JS stacktrace --->
FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
<--- Last few GCs --->
<--- JS stacktrace --->
#
# Fatal javascript OOM in MemoryChunk allocation failed during deserialization.
#
I am running a new build with plasmo 0.85.2 now
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
I will bump to latest; (this is github actions runners; First log from my machine but it crashes/freezes)
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
Ok will retry with two different steps -- 
# plasmo build
🟢 DONE   | Finished in 36524ms!
Done in 44.66s.
yarn run v1.22.22
warning package.json: No license field
# plasmo package
$ plasmo package --verbose
🟡 0      | Running command: package
🟣 Plasmo v0.84.1
🔴 The Browser Extension Framework
🟠 WARN   | A new version of plasmo is available: v0.85.2
          | Run "yarn add [email protected]" to update
🔵 INFO   | Prepare to package the extension bundle...
🟡 1      | Creating Manifest Factory...
🟡 2      | Ensure exists: /home/runner/work/extension/extension/.plasmo
🟡 3      | /home/runner/work/extension/extension/assets/icon.png found, creating resized icons
🟡 4      | Creating static templates for popup
(...)
🟡 14     | Parsed config: { matches: [ '<all_urls>' ], world: 'MAIN', run_at: 'document_start' }
🟡 15     | Adding content script:  /home/runner/work/extension/extension/src/contents/inpage.ts
🟡 16     | Parsed config: { matches: [ '<all_urls>' ], all_frames: true }
🟡 17     | Adding content script:  /home/runner/work/extension/extension/src/contents/worker.ts
🟡 18     | { messageHandlerList: [], portHandlerList: [] }
🟡 19     | Creating BGSW entry
🟡 20     | Hash changed, updating manifest
<--- Last few GCs --->
<--- JS stacktrace --->
FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
<--- Last few GCs --->
<--- JS stacktrace --->
FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
<--- Last few GCs --->
<--- JS stacktrace --->
#
# Fatal javascript OOM in MemoryChunk allocation failed during deserialization.
#
<--- Last few GCs --->
<--- JS stacktrace --->
FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
<--- Last few GCs --->
<--- JS stacktrace --->
#
# Fatal javascript OOM in MemoryChunk allocation failed during deserialization.
#
# plasmo build
🟢 DONE   | Finished in 36524ms!
Done in 44.66s.
yarn run v1.22.22
warning package.json: No license field
# plasmo package
$ plasmo package --verbose
🟡 0      | Running command: package
🟣 Plasmo v0.84.1
🔴 The Browser Extension Framework
🟠 WARN   | A new version of plasmo is available: v0.85.2
          | Run "yarn add [email protected]" to update
🔵 INFO   | Prepare to package the extension bundle...
🟡 1      | Creating Manifest Factory...
🟡 2      | Ensure exists: /home/runner/work/extension/extension/.plasmo
🟡 3      | /home/runner/work/extension/extension/assets/icon.png found, creating resized icons
🟡 4      | Creating static templates for popup
(...)
🟡 14     | Parsed config: { matches: [ '<all_urls>' ], world: 'MAIN', run_at: 'document_start' }
🟡 15     | Adding content script:  /home/runner/work/extension/extension/src/contents/inpage.ts
🟡 16     | Parsed config: { matches: [ '<all_urls>' ], all_frames: true }
🟡 17     | Adding content script:  /home/runner/work/extension/extension/src/contents/worker.ts
🟡 18     | { messageHandlerList: [], portHandlerList: [] }
🟡 19     | Creating BGSW entry
🟡 20     | Hash changed, updating manifest
<--- Last few GCs --->
<--- JS stacktrace --->
FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
<--- Last few GCs --->
<--- JS stacktrace --->
FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
<--- Last few GCs --->
<--- JS stacktrace --->
#
# Fatal javascript OOM in MemoryChunk allocation failed during deserialization.
#
<--- Last few GCs --->
<--- JS stacktrace --->
FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
<--- Last few GCs --->
<--- JS stacktrace --->
#
# Fatal javascript OOM in MemoryChunk allocation failed during deserialization.
#
as it failed here
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
Ok will try after this attempt
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
cf. 
    "build": "plasmo build",
    "dev": "plasmo dev",
    "format:write": "prettier . --write",
    "lint": "eslint . --ext .ts,.tsx",
    "lint:fix": "eslint . --ext .ts,.tsx --fix",
    "type:check": "tsc --noEmit",
    "package": "plasmo package",
    "build": "plasmo build",
    "dev": "plasmo dev",
    "format:write": "prettier . --write",
    "lint": "eslint . --ext .ts,.tsx",
    "lint:fix": "eslint . --ext .ts,.tsx --fix",
    "type:check": "tsc --noEmit",
    "package": "plasmo package",
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
No description
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
What would you advise to debug @lab what makes this resource issue? I tried --verbose but nothing; We tried with a VM with 64GB or 128GB and it fails
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
What is strange it is throwing there -- at new Worker (node:internal/worker:291:19) at wk (file:///Users/dp/work/extension/node_modules/fflate/esm/index.mjs:22:13) at wrkr (file:///Users/dp/work/extension/node_modules/fflate/esm/index.mjs:893:12) at astrmify (file:///Users/dp/work/extension/node_modules/fflate/esm/index.mjs:930:13) at new AsyncDeflate (file:///Users/dp/work/extension/node_modules/fflate/esm/index.mjs:1086:9) at new AsyncZipDeflate (file:///Users/dp/work/extension/node_modules/fflate/esm/index.mjs:1949:18) at file:///Users/dp/work/extension/node_modules/plasmo/dist/index.js:166:10563 at new Promise (<anonymous>) at Qr (file:///Users/dp/work/extension/node_modules/plasmo/dist/index.js:166:10341) at async Zh (file:///Users/dp/work/extension/node_modules/plasmo/dist/index.js:166:11510) AsyncZipDeflate
79 replies
PD🧩 Plasmo Developers
Created by dp on 3/21/2024 in #👾extension
Bug : EAGAIN when use `plasmo package`
@lab @LoXatoR fyi
79 replies