Deployment error missing deps

[ShaMan123]

Environment information

System:
  OS: macOS 15.7.3
  CPU: (12) arm64 Apple M2 Max
  Memory: 6.43 GB / 32.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 22.18.0 - /Users/shaman123/.nvm/versions/node/v22.18.0/bin/node
  Yarn: 1.22.22 - /opt/homebrew/bin/yarn
  npm: 11.6.2 - /Users/shaman123/.nvm/versions/node/v22.18.0/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/auth-construct: 1.10.0
  @aws-amplify/backend: 1.19.0
  @aws-amplify/backend-ai: Not Found
  @aws-amplify/backend-auth: 1.9.0
  @aws-amplify/backend-cli: 1.8.1
  @aws-amplify/backend-data: 1.6.2
  @aws-amplify/backend-deployer: 2.1.4
  @aws-amplify/backend-function: 1.15.2
  @aws-amplify/backend-output-schemas: 1.7.1
  @aws-amplify/backend-output-storage: 1.3.2
  @aws-amplify/backend-secret: 1.4.2
  @aws-amplify/backend-storage: 1.4.2
  @aws-amplify/cli-core: 2.2.3
  @aws-amplify/client-config: 1.9.1
  @aws-amplify/data-construct: 1.16.3
  @aws-amplify/data-schema: 1.22.0
  @aws-amplify/deployed-backend-client: 1.8.1
  @aws-amplify/form-generator: 1.2.6
  @aws-amplify/model-generator: 1.2.2
  @aws-amplify/platform-core: 1.10.3
  @aws-amplify/plugin-types: 1.11.1
  @aws-amplify/sandbox: 2.1.4
  @aws-amplify/schema-generator: 1.4.1
  @aws-cdk/toolkit-lib: 1.6.1
  aws-amplify: 6.15.9
  aws-cdk-lib: 2.233.0
  typescript: 5.9.3
npm warn exec The following package was not found and will be installed: cdk@2.1100.1
No AWS environment variables
No CDK environment variables

Describe the bug

Getting this error from the deployment logs.
This does not happen locally when running npm ci.
My backend is linux.

npm error code EUSAGE

npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
                                    
npm error Missing: @csstools/css-parser-algorithms@3.0.5 from lock file

npm error Missing: @csstools/css-tokenizer@3.0.4 from lock file

Running npm ls @csstools/css-parser-algorithms shows

└── (empty)

Reproduction steps

Follow https://docs.amplify.aws/javascript/start/manual-installation/ and deploy an amplify app.

Is amplify the recommended approach for full stack apps or has it been deprecated?

Adding @csstools/css-parser-algorithms and @csstools/css-tokenizer to deps makes the deployment succeed

[pahud]

Thank you for reporting this issue, @ShaMan123!

This appears to be a cross-platform dependency resolution issue where your package-lock.json was generated on macOS but doesn't include all dependencies needed when running on Linux (Amplify Hosting's build environment).

Immediate Workarounds

Option 1: Regenerate your lock file

rm package-lock.json
npm install
git add package-lock.json
git commit -m "Regenerate lock file"
git push

Option 2: Use npm install in your build
In your amplify.yml, change npm ci to npm install:

backend:
  phases:
    build:
      commands:
        - npm install

Questions to Help Us Investigate

1. Could you share your package.json (with any sensitive info redacted)?
2. Are you using any CSS processing libraries (PostCSS, Tailwind, etc.)?
3. When did this issue start occurring? Was there a recent dependency update?

To Answer Your Question

Is amplify the recommended approach for full stack apps or has it been deprecated?

Amplify Gen 2 is actively maintained and recommended for full-stack applications. This issue is related to npm's cross-platform dependency resolution, not Amplify deprecation.

[ShaMan123]

I am using mui without additional CSS processing.
I am using vite react SWC rather than the regular vite react plugin (seems to cause issues with assets).
I am using node 24 on both my local env and hosted env (upgraded after build failure).

The issue occurred from the start. I followed an amplify getting started guide and tried to deploy my FE app but it failed. I investigated the logs and decided to install the mentioned packages that were mismatching between environments and then the build and deployment succeeded.
I prefer this solution over not running npm ci upon deployment.

{
  "name": "REDACTED",
  "private": true,
  "version": "0.0.1",
  "type": "module",
  "scripts": {
    "dev": "vite",
    "test": "vitest run",
    "build": "tsc -b && vite build",
    "lint": "eslint .",
    "preview": "vite preview"
  },
  "dependencies": {
    "@dnd-kit/helpers": "^0.1.21",
    "@dnd-kit/react": "^0.1.21",
    "@emotion/react": "^11.14.0",
    "@emotion/styled": "^11.14.1",
    "@lexical/react": "^0.38.2",
    "@mui/icons-material": "^7.3.5",
    "@mui/lab": "^7.0.1-beta.19",
    "@mui/material": "^7.3.5",
    "aws-amplify": "^6.15.9",
    "diff": "^8.0.2",
    "happy-dom": "^20.0.10",
    "idb": "^8.0.3",
    "jwt-decode": "^4.0.0",
    "lexical": "^0.38.2",
    "lodash.debounce": "^4.0.8",
    "lodash.groupby": "^4.6.0",
    "lodash.isequal": "^4.5.0",
    "lodash.merge": "^4.6.2",
    "lodash.partition": "^4.6.0",
    "react": "^19.2.1",
    "react-dom": "^19.2.1",
    "react-router": "^7.9.5",
    "react-virtuoso": "^4.15.0",
    "xlsx": "https://cdn.sheetjs.com/xlsx-0.20.3/xlsx-0.20.3.tgz"
  },
  "devDependencies": {
    "@aws-amplify/backend": "^1.19.0",
    "@aws-amplify/backend-cli": "^1.8.1",
    "@csstools/css-parser-algorithms": "^3.0.5",
    "@csstools/css-tokenizer": "^3.0.4",
    "@eslint/js": "^9.39.1",
    "@testing-library/react": "^16.3.0",
    "@types/lodash.debounce": "^4.0.9",
    "@types/lodash.groupby": "^4.6.9",
    "@types/lodash.isequal": "^4.5.8",
    "@types/lodash.merge": "^4.6.9",
    "@types/lodash.partition": "^4.6.9",
    "@types/lodash.set": "^4.3.9",
    "@types/node": "^24.10.1",
    "@types/react": "^19.1.16",
    "@types/react-dom": "^19.1.9",
    "@vitejs/plugin-react-swc": "^4.1.0",
    "constructs": "^10.4.4",
    "esbuild": "^0.27.2",
    "eslint": "^9.36.0",
    "eslint-plugin-react-hooks": "^5.2.0",
    "eslint-plugin-react-refresh": "^0.4.22",
    "globals": "^16.4.0",
    "tsx": "^4.21.0",
    "typescript": "^5.9.3",
    "typescript-eslint": "^8.45.0",
    "vite": "^7.1.7",
    "vitest": "^4.0.8"
  }
}

[ShaMan123]

BTW running npm i logs a lot of warnings regarding deprecated packages used by amplify packages. That is what made me think amplify is deprecated or outdated.

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @aws-amplify/plugin-types@1.10.1
npm warn Found: @aws-sdk/types@3.821.0
npm warn node_modules/@aws-amplify/data-construct/node_modules/@aws-amplify/ai-constructs/node_modules/@aws-amplify/plugin-types/node_modules/@aws-sdk/types
npm warn
npm warn Could not resolve dependency:
npm warn peer @aws-sdk/types@"^3.734.0" from @aws-amplify/plugin-types@1.10.1
npm warn node_modules/@aws-amplify/data-construct/node_modules/@aws-amplify/ai-constructs/node_modules/@aws-amplify/plugin-types
npm warn   @aws-amplify/plugin-types@"^1.10.1" from @aws-amplify/ai-constructs@1.5.3
npm warn   node_modules/@aws-amplify/data-construct/node_modules/@aws-amplify/ai-constructs
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @aws-amplify/plugin-types@1.10.1
npm warn Found: @aws-sdk/types@3.821.0
npm warn node_modules/@aws-amplify/graphql-api-construct/node_modules/@aws-amplify/ai-constructs/node_modules/@aws-amplify/plugin-types/node_modules/@aws-sdk/types
npm warn
npm warn Could not resolve dependency:
npm warn peer @aws-sdk/types@"^3.734.0" from @aws-amplify/plugin-types@1.10.1
npm warn node_modules/@aws-amplify/graphql-api-construct/node_modules/@aws-amplify/ai-constructs/node_modules/@aws-amplify/plugin-types
npm warn   @aws-amplify/plugin-types@"^1.10.1" from @aws-amplify/ai-constructs@1.5.3
npm warn   node_modules/@aws-amplify/graphql-api-construct/node_modules/@aws-amplify/ai-constructs
npm warn deprecated inflight@1.0.6: 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 @babel/plugin-proposal-class-properties@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated @babel/plugin-proposal-object-rest-spread@7.20.7: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead
npm warn deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.