adobe / adobe/reactor-uploader
Newer ECMAScript is not supported by Launch
- Dominant language
- JavaScript
- Stars
- 10
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
In my Web Vitals extension, I bundle the JS library for ease of implementation by users. However, when I bundle the latest Web Vitals JS library v5.1.0 (available at https://unpkg.com/web-vitals@5/dist/web-vitals.attribution.iife.js), then I get the below error when uploading my extension:
```
Error: Extension package processing failed.
id: c8eae0ef-90df-4d4f-8f55-8b2d4b1b39e7
code: unsupported-ecma-version
meta:
request_id: ZQ15UWG9mSFmOTldGkDP7Fl4acFSLLX9
title: Unsupported ECMA Version
detail: Code using an unsupported ECMAScript version was detected
source:
at requestStatus (/path/to/extension/node_modules/@adobe/reactor-uploader/bin/monitorStatus.js:62:11)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async /path/to/extension/node_modules/@adobe/reactor-uploader/bin/index.js:105:5
Node.js v24.13.0
```
I don't get this error when I bundle the Web Vitals JS library v4.2.4.
This issue is not critical to my extension's operations, but would be good if Launch could support newer versions of ECMAScript.
Contributor guide
Research direction
Start with the upload and status-monitoring entry points shown in @adobe/reactor-uploader/bin/index.js and bin/monitorStatus.js, then reproduce the extension upload with web-vitals v5.1.0 and v4.2.4. Trace where the unsupported ECMAScript version is detected or reported. Done means an extension containing the newer bundle can upload successfully while existing uploads remain supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100