-
Notifications
You must be signed in to change notification settings - Fork 35
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
When using Node 18 LTS and installing there is an unsupported engine error that occurs.
Package version
1.1.11
To Reproduce
Using Node LTS 18.16.0,
- Start a new CRA project, (
npx create-react-app my-app) - Update the
package.jsonfiledependenciesto be what is below:
"@adobe/aem-core-components-react-base": "^1.1.8",
"@adobe/aem-core-components-react-spa": "^1.2.0",
"@adobe/aem-react-editable-components": "^1.1.10",
"@adobe/aem-spa-component-mapping": "^1.1.1",
"@adobe/aem-spa-page-model-manager": "^1.3.11",
"@testing-library/jest-dom": "^5.15.0",
"@testing-library/react": "^11.2.7",
"@testing-library/user-event": "^12.8.3",
"react": "^16.14.0",
"react-dom": "^16.14.0",
"react-scripts": "5.0.1",
"web-vitals": "^2.1.4"
- Remove
node_modulesandpackage-lock.jsonfile/folder - run
npm iagain - notice warnings.
Expected behavior
Packages are compatible and compile correctly without unsupported engine notifications.
Screenshots

^ Warnings Image ^
Additional context
Seems you cannot upgrade the package since there are peer dependency issues when using the various adobe spa packages.
using --legacy-peer-deps may introduce unknown stability issues.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
