Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] ELIFECYCLE Command failed with exit code 3221226356. #1142

Open
2 of 3 tasks
abhigyantrips opened this issue Dec 6, 2024 · 2 comments
Open
2 of 3 tasks

[BUG] ELIFECYCLE Command failed with exit code 3221226356. #1142

abhigyantrips opened this issue Dec 6, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@abhigyantrips
Copy link

What happened?

i've used plasmo for building a Chrome extension before, but this is my first time trying out multi-platform development with process.env.PLASMO_BROWSER. every time i've tried to run pnpm dev, i've just received an ELIFECYCLE error (with no further explanation in the verbose section).

here is my package.json for reference. the overrides are from an audit fix and i've tried out plasmo dev without them too (still got the same error).

{
  "name": "...",
  "displayName": "...",
  "version": "0.0.1",
  "description": "...",
  "author": "Abhigyan Trips <contact@abhigyantrips.dev>",
  "homepage": "...",
  "scripts": {
    "dev": "plasmo dev",
    "build": "plasmo build",
    "package": "plasmo package"
  },
  "dependencies": {
    "plasmo": "0.89.4",
    "react": "18.2.0",
    "react-dom": "18.2.0"
  },
  "devDependencies": {
    "@ianvs/prettier-plugin-sort-imports": "^4.4.0",
    "@types/chrome": "0.0.258",
    "@types/firefox-webext-browser": "^120.0.4",
    "@types/node": "20.11.5",
    "@types/react": "18.2.48",
    "@types/react-dom": "18.2.18",
    "prettier": "3.2.4",
    "prettier-plugin-tailwindcss": "^0.6.9",
    "typescript": "5.3.3"
  },
  "manifest": {
    "permissions": [
      "storage"
    ],
    "host_permissions": [
      "*://www.instagram.com/*"
    ]
  },
  "pnpm": {
    "overrides": {
      "msgpackr@<1.10.1": ">=1.10.1",
      "svelte@<4.2.19": ">=4.2.19"
    }
  }
}

i've also tried out building for firefox as a specific target which works out completely fine. it's the dev that's an issue here.

my extension is basically a content.ts file that's using some typescript types and config vars from other files. if the error was because of missing tokens though i would've expected that to pop up in the CLI.

Version

Latest

What OS are you seeing the problem on?

Windows

What browsers are you seeing the problem on?

Chrome, Firefox

Relevant log output

PS F:\ZenGram> pnpm run dev --verbose

> zengram@0.0.1 dev F:\ZenGram
> plasmo dev "--verbose"

🟡 0      | Running command: dev
🟣 Plasmo v0.89.4
🔴 The Browser Extension Framework
🔵 INFO   | Starting the extension development server...
🟡 1      | Starting dev server on localhost:1012, HMR on localhost:1815...
🔵 INFO   | Building for target: chrome-mv3
🟡 2      | Creating Manifest Factory...
🟡 3      | Ensure exists: F:\ZenGram\.plasmo
🟡 4      | F:\ZenGram\assets\icon.png found, creating resized icons
🟡 5      | Creating static templates for popup
🟡 6      | Creating static templates for options
🟡 7      | Creating static templates for newtab
🟡 8      | Creating static templates for devtools
🟡 9      | Creating static templates for sidepanel
🟡 10     | Parsed config: { matches: [ '*://www.instagram.com/*' ], run_at: 'document_start' }
🟡 11     | Adding content script:  F:\ZenGram\src\content.ts
🟡 12     | {
  messageHandlerList: [],
  externalMessageHandlerList: [],
  portHandlerList: []
}
🟡 13     | Hash changed, updating manifest
🟡 14     | Watching the following files: Set(135) {
  'F:\\ZenGram\\package.json',
  'F:\\ZenGram\\src\\.env.chrome.local',
  'F:\\ZenGram\\src\\.env.dev.local',
  'F:\\ZenGram\\src\\.env.development.local',
  'F:\\ZenGram\\src\\.env.local',
  'F:\\ZenGram\\src\\.env.chrome',
  'F:\\ZenGram\\src\\.env.dev',
  'F:\\ZenGram\\src\\.env.development',
  'F:\\ZenGram\\src\\.env',
  'F:\\ZenGram\\src\\content.chrome.ts',
  'F:\\ZenGram\\src\\content.development.ts',
  'F:\\ZenGram\\src\\content.ts',
  'F:\\ZenGram\\src\\content.chrome.tsx',
  'F:\\ZenGram\\src\\content.development.tsx',
  'F:\\ZenGram\\src\\content.tsx',
  'F:\\ZenGram\\src\\content.chrome.jsx',
  'F:\\ZenGram\\src\\content.development.jsx',
  'F:\\ZenGram\\src\\content.jsx',
  'F:\\ZenGram\\src\\content.chrome.js',
  'F:\\ZenGram\\src\\content.development.js',
  'F:\\ZenGram\\src\\content.js',
  'F:\\ZenGram\\src\\sandbox.chrome.ts',
  'F:\\ZenGram\\src\\sandbox.development.ts',
  'F:\\ZenGram\\src\\sandbox.ts',
  'F:\\ZenGram\\src\\sandbox.chrome.tsx',
  'F:\\ZenGram\\src\\sandbox.development.tsx',
  'F:\\ZenGram\\src\\sandbox.tsx',
  'F:\\ZenGram\\src\\sandbox.chrome.jsx',
  'F:\\ZenGram\\src\\sandbox.development.jsx',
  'F:\\ZenGram\\src\\sandbox.jsx',
  'F:\\ZenGram\\src\\sandbox.chrome.js',
  'F:\\ZenGram\\src\\sandbox.development.js',
  'F:\\ZenGram\\src\\sandbox.js',
  'F:\\ZenGram\\src\\background.chrome.ts',
  'F:\\ZenGram\\src\\background\\index.chrome.ts',
  'F:\\ZenGram\\src\\background.development.ts',
  'F:\\ZenGram\\src\\background\\index.development.ts',
  'F:\\ZenGram\\src\\background.ts',
  'F:\\ZenGram\\src\\background\\index.ts',
  'F:\\ZenGram\\src\\background.chrome.js',
  'F:\\ZenGram\\src\\background\\index.chrome.js',
  'F:\\ZenGram\\src\\background.development.js',
  'F:\\ZenGram\\src\\background\\index.development.js',
  'F:\\ZenGram\\src\\background.js',
  'F:\\ZenGram\\src\\background\\index.js',
  'F:\\ZenGram\\src\\popup.chrome.tsx',
  'F:\\ZenGram\\src\\popup\\index.chrome.tsx',
  'F:\\ZenGram\\src\\popup.development.tsx',
  'F:\\ZenGram\\src\\popup\\index.development.tsx',
  'F:\\ZenGram\\src\\popup.tsx',
  'F:\\ZenGram\\src\\popup\\index.tsx',
  'F:\\ZenGram\\src\\popup.chrome.jsx',
  'F:\\ZenGram\\src\\popup\\index.chrome.jsx',
  'F:\\ZenGram\\src\\popup.development.jsx',
  'F:\\ZenGram\\src\\popup\\index.development.jsx',
  'F:\\ZenGram\\src\\popup.jsx',
  'F:\\ZenGram\\src\\popup\\index.jsx',
  'F:\\ZenGram\\src\\options.chrome.tsx',
  'F:\\ZenGram\\src\\options\\index.chrome.tsx',
  'F:\\ZenGram\\src\\options.development.tsx',
  'F:\\ZenGram\\src\\options\\index.development.tsx',
  'F:\\ZenGram\\src\\options.tsx',
  'F:\\ZenGram\\src\\options\\index.tsx',
  'F:\\ZenGram\\src\\options.chrome.jsx',
  'F:\\ZenGram\\src\\options\\index.chrome.jsx',
  'F:\\ZenGram\\src\\options.development.jsx',
  'F:\\ZenGram\\src\\options\\index.development.jsx',
  'F:\\ZenGram\\src\\options.jsx',
  'F:\\ZenGram\\src\\options\\index.jsx',
  'F:\\ZenGram\\src\\devtools.chrome.tsx',
  'F:\\ZenGram\\src\\devtools\\index.chrome.tsx',
  'F:\\ZenGram\\src\\devtools.development.tsx',
  'F:\\ZenGram\\src\\devtools\\index.development.tsx',
  'F:\\ZenGram\\src\\devtools.tsx',
  'F:\\ZenGram\\src\\devtools\\index.tsx',
  'F:\\ZenGram\\src\\devtools.chrome.jsx',
  'F:\\ZenGram\\src\\devtools\\index.chrome.jsx',
  'F:\\ZenGram\\src\\devtools.development.jsx',
  'F:\\ZenGram\\src\\devtools\\index.development.jsx',
  'F:\\ZenGram\\src\\devtools.jsx',
  'F:\\ZenGram\\src\\devtools\\index.jsx',
  'F:\\ZenGram\\src\\newtab.chrome.tsx',
  'F:\\ZenGram\\src\\newtab\\index.chrome.tsx',
  'F:\\ZenGram\\src\\newtab.development.tsx',
  'F:\\ZenGram\\src\\newtab\\index.development.tsx',
  'F:\\ZenGram\\src\\newtab.tsx',
  'F:\\ZenGram\\src\\newtab\\index.tsx',
  'F:\\ZenGram\\src\\newtab.chrome.jsx',
  'F:\\ZenGram\\src\\newtab\\index.chrome.jsx',
  'F:\\ZenGram\\src\\newtab.development.jsx',
  'F:\\ZenGram\\src\\newtab\\index.development.jsx',
  'F:\\ZenGram\\src\\newtab.jsx',
  'F:\\ZenGram\\src\\newtab\\index.jsx',
  'F:\\ZenGram\\src\\sidepanel.chrome.tsx',
  'F:\\ZenGram\\src\\sidepanel\\index.chrome.tsx',
  'F:\\ZenGram\\src\\sidepanel.development.tsx',
  'F:\\ZenGram\\src\\sidepanel\\index.development.tsx',
  'F:\\ZenGram\\src\\sidepanel.tsx',
  'F:\\ZenGram\\src\\sidepanel\\index.tsx',
  'F:\\ZenGram\\src\\sidepanel.chrome.jsx',
  ... 35 more items
}
🔵 INFO   | Loaded environment variables from: []
(node:32624) [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🟡 0      | @plasmohq/parcel-transformer-manifest
🟡 1      | Adding icons
🟡 2      | Adding default_icon
🟡 3      | Adding default_popup
🟡 4      | + Finished transforming manifest
🔄 Building..🟡 0      | @plasmohq/parcel-bundler
🔄 Building...🟡 0      | @plasmohq/parcel-runtime Injecting << script-runtime >> for content.[hash].js b7e7b9da480c00a3 F:\ZenGram\src\content.ts
🟡 1      | @plasmohq/parcel-runtime Injecting << page-runtime >> for popup.[hash].js 585f4e9c7d3dc21e F:\ZenGram\.plasmo\static\popup.tsx
🟡 2      | @plasmohq/parcel-runtime Injecting << background-service-runtime >> for plasmo-default-background.[hash].js 8415c5525fdd9bcb F:\ZenGram\node_modules\.pnpm\@plasmohq+parcel-transformer-manifest@0.20.1\node_modules\@plasmohq\parcel-transformer-manifest\runtime\plasmo-default-background.ts
 ELIFECYCLE  Command failed with exit code 3221225477.

(OPTIONAL) Contribution

  • I would like to fix this BUG via a PR

Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I checked the current issues for duplicate problems.
@abhigyantrips abhigyantrips added the bug Something isn't working label Dec 6, 2024
@abhigyantrips
Copy link
Author

abhigyantrips commented Dec 7, 2024

also facing this issue in yarn (realizing the problem might not be with packages f)

edit: it did dev and build perfectly fine in WSL.

@abhigyantrips
Copy link
Author

right now i'm getting around this by using yarn in WSL, but yeah even then saving the files does not update the extension while using yarn dev. checked in --verbose and there's no output at all after every save

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant