plasmo icon indicating copy to clipboard operation
plasmo copied to clipboard

[BUG] Running standard examples fails

Open ThibaultJanBeyer opened this issue 1 year ago β€’ 3 comments

What happened?

Running standard examples fails i.e.:

  • Running pnpm create plasmo --with-supabase --with-tailwindcss gives me build failures (see logs below)

These standards should work, no? Also I've hard times debugging, often I just get:

πŸ”„ Building..node(70031,0x1711d7000) malloc: Incorrect checksum for freed object 0x135ac1e00: probably modified after being freed.
Corrupt value: 0x0
node(70031,0x1711d7000) malloc: *** set a breakpoint in malloc_error_break to debug
node(70031,0x1715e3000) malloc: Incorrect checksum for freed object 0x136316800: probably modified after being freed.
Corrupt value: 0x3932383338356433
node(70031,0x1715e3000) malloc: *** set a breakpoint in malloc_error_break to debug

or

(node:13618) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
πŸ”„ Building..node(13618,0x17b3c7000) malloc: Incorrect checksum for freed object 0x15abc2400: probably modified after being freed.
Corrupt value: 0x0
node(13618,0x17abaf000) malloc: Incorrect checksum for freed object 0x11a9ca200: probably modified after being freed.
Corrupt value: 0x0
node(13618,0x17b3c7000) malloc: *** set a breakpoint in malloc_error_break to debug
node(13618,0x17abaf000) malloc: *** set a breakpoint in malloc_error_break to debug
node(13618,0x17b7d3000) malloc: Incorrect checksum for freed object 0x14a9c1000: probably modified after being freed.
Corrupt value: 0x0
node(13618,0x17b7d3000) malloc: *** set a breakpoint in malloc_error_break to debug
 ELIFECYCLE  Command failed.

Which doesn't tell me anything about where the issue is?

Thanks!

Version

Latest

What OS are you seeing the problem on?

MacOSX

What browsers are you seeing the problem on?

Chrome

Relevant log output

🟒 DONE   | Extension re-packaged in 218ms! πŸš€
πŸ”΄ ERROR  | Build failed. To debug, run plasmo dev --verbose.
πŸ”΄ ERROR  | The expression evaluated to a falsy value:

  (0, \_assert().default)(internalBundleGraph != null)

πŸ”΄ ERROR  | Build failed. To debug, run plasmo dev --verbose.
πŸ”΄ ERROR  | The expression evaluated to a falsy value:

  (0, \_assert().default)(internalBundleGraph != null)

πŸ”΄ ERROR  | Build failed. To debug, run plasmo dev --verbose.
πŸ”΄ ERROR  | The expression evaluated to a falsy value:

  (0, \_assert().default)(internalBundleGraph != null)

πŸ”΄ ERROR  | Build failed. To debug, run plasmo dev --verbose.
πŸ”΄ ERROR  | The expression evaluated to a falsy value:

  (0, \_assert().default)(internalBundleGraph != null)

πŸ”΄ ERROR  | Build failed. To debug, run plasmo dev --verbose.
πŸ”΄ ERROR  | The expression evaluated to a falsy value:

  (0, \_assert().default)(internalBundleGraph != null)

(OPTIONAL) Contribution

  • [ ] I would like to fix this BUG via a PR

Code of Conduct

  • [X] I agree to follow this project's Code of Conduct
  • [X] I checked the current issues for duplicate problems.

ThibaultJanBeyer avatar Dec 17 '24 07:12 ThibaultJanBeyer

Nevermind, for some reasons it worked smoothly now? I suspect network issues

ThibaultJanBeyer avatar Dec 17 '24 09:12 ThibaultJanBeyer

Actually now I have it again… I have no idea what it is, it seems to happen randomly

ThibaultJanBeyer avatar Dec 17 '24 09:12 ThibaultJanBeyer

Hi, could you update your issue to include your PNPM and Node version please πŸ™

pippinmole avatar Feb 09 '25 10:02 pippinmole