Describe the bug

When creating a new project using the latest Ignite CLI (IR), I encountered two separate issues on a fresh project setup:

1️⃣ NPM dependency conflict

On first running the Ignite CLI and during the automatic npm install, the following error occurs:

Error: Command failed: npm install
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react-native-worklets
npm error   react-native-worklets@"0.7.0-nightly-20251001-14eca5b4c" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react-native-worklets@">=0.5.0" from [email protected]
npm error node_modules/react-native-reanimated
npm error   react-native-reanimated@"~4.1.1" from the root project
npm error   peer react-native-reanimated@">= 2.0.0" from [email protected]
npm error     node_modules/react-native-drawer-layout
npm error       react-native-drawer-layout@"^4.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

Workaround: Running npm install --legacy-peer-deps resolves this, but it seems the default Ignite project scaffolding is generating a dependency tree that conflicts with current npm peer resolution rules.

2️⃣ Missing ErrorBoundary component

After installing dependencies, running expo run:ios fails with:

[React] Unable to resolve module @/components/ErrorBoundary/ErrorBoundary from src/app/_layout.tsx
Unable to resolve "@/components/ErrorBoundary/ErrorBoundary" from "src/app/_layout.tsx"
  21 | export { ErrorBoundary } from "@/components/ErrorBoundary/ErrorBoundary"

The _layout.tsx file includes the line:

export { ErrorBoundary } from "@/components/ErrorBoundary/ErrorBoundary"

However, Ignite does not scaffold the ErrorBoundary component in src/components/ErrorBoundary/ErrorBoundary.tsx.

Impact: This prevents the freshly scaffolded project from running without manually either creating the component or removing the import/export.

Steps to reproduce:

npx ignite-cli new MyProject

Observe npm install failure due to react-native-worklets / react-native-reanimated peer conflict

Run expo run:ios

Observe missing ErrorBoundary module error

Ignite version

11.2.0

Additional info

lukeholmgren@Lukes-MacBook-Pro-2 dunk-data % npx ignite-cli doctor
Need to install the following packages:
[email protected]
Ok to proceed? (y)

npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
System
platform darwin
arch arm64
cpu 14 cores Apple M4 Max
directory dunk-data /Users/lukeholmgren/Documents/GitHub/dunk-data
/Users/lukeholmgren/.npm/_npx/e31027f3785124a8/node_modules/gluegun/build/index.js:15
throw up;
^

TypeError: Cannot read properties of null (reading 'split')
at Command. (/Users/lukeholmgren/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build/commands/doctor.js:49:59)
at Generator.next ()
at fulfilled (/Users/lukeholmgren/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build/commands/doctor.js:5:58)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

Node.js v23.8.0