hs project lint reports root package missing UI extension lint deps in app-card projects

[luxferre]

Summary

hs project lint appears to treat every package.json discovered in a Developer Platform project as a UI extension lint target.

For app-card projects, HubSpot docs place app cards under src/app/cards, with the card package and dependencies in the cards/ directory. If the repository also has a root package.json for unrelated repo tooling, hs project lint reports that root package as missing UI extension lint dependencies and can prompt to install those dependencies at the root.

The root package may have its own linting dependencies/scripts, but its behavior is not the app-card linting contract. The important expectation is that app cards are linted from their own src/app/cards package and node_modules context.

Version

• @hubspot/cli: 8.6.0
• Project platform: 2025.2

Relevant docs

The app card reference says app card components are defined within a cards directory under app/, and that the cards directory should contain the card package.json:

https://developers.hubspot.com/docs/apps/developer-platform/build-apps/features/app-cards/reference

The create app card guide says hs project add creates the card files in src/app/cards, including package.json, and hs project install-deps updates the cards/ directory with node_modules and package-lock.json:

https://developers.hubspot.com/docs/apps/developer-platform/build-apps/features/app-cards/create-an-app-card

Project shape

hsproject.json
package.json                 # repo/root tooling, not an app-card package
package-lock.json
src/
  app/
    cards/
      package.json           # app-card package
      package-lock.json
      node_modules/
      eslint.config.js
      ...card sources...

Steps to reproduce

No HubSpot auth/profile is required for the repro.

1. Create a Developer Platform app-card project with platformVersion: "2025.2" and srcDir: "src".
2. Keep the app-card package at src/app/cards/package.json.
3. Add a root package.json for unrelated repo tooling.
4. Run the non-mutating lint command:

npx hs project lint --install-missing-deps=false

Optionally run the default command to see the install prompt:

npx hs project lint

Actual behavior

hs project lint checks both the root package and src/app/cards as UI extension lint locations.

With --install-missing-deps=false, it reports the root package as missing UI extension lint dependencies. With the default interactive command, it can prompt to install UI extension lint dependencies into the root package.

Expected behavior

hs project lint should lint app cards from the app-card package directory, e.g. src/app/cards, using that package's dependencies and node_modules.

The root package can exist for repository tooling, but it should not be required to contain HubSpot UI extension lint dependencies just because app cards exist under src/app/cards. Root package linting behavior can be undefined, but it should not block or mutate card linting.

Notes

This may be a regression, but I am not certain. The problematic behavior is applying the required UI extension lint dependency set to non-card package locations.

[luxferre]

Additional concrete package layout from the project where I reproduced this.

I invoked the locally installed CLI through globally installed npx, not a globally installed hs binary:

npx hs project lint --install-missing-deps=false

Root package.json:

{
  "name": "example-hubspot-connector",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "hs:upload": "bash ./scripts/hs-project.sh upload",
    "hs:deploy": "bash ./scripts/hs-project.sh deploy"
  },
  "devDependencies": {
    "@hubspot/cli": "^8.6.0"
  }
}

src/app/cards/package.json:

{
  "name": "example-hubspot-app-cards",
  "version": "1.0.0",
  "license": "MIT",
  "dependencies": {
    "@hubspot/ui-extensions": "^0.13.1",
    "react": "^18.2.0",
    "try": "^1.0.3",
    "uuid": "^13.0.0",
    "zod": "^4.3.5"
  },
  "devDependencies": {
    "@intlayer/cli": "^6.1.6",
    "@stylistic/eslint-plugin": "^5.6.1",
    "@types/react": "^18.3.26",
    "@typescript-eslint/eslint-plugin": "^8.51.0",
    "@typescript-eslint/parser": "^8.51.0",
    "eslint": "^9.39.2",
    "eslint-import-resolver-typescript": "^4.4.4",
    "eslint-plugin-import-x": "^4.16.1",
    "eslint-plugin-jsonc": "^2.21.0",
    "eslint-plugin-perfectionist": "^5.3.1",
    "eslint-plugin-react": "^7.37.5",
    "eslint-plugin-react-hooks": "^7.0.1",
    "intlayer": "^6.1.6",
    "jiti": "^2.6.1",
    "jsonc-eslint-parser": "^2.4.2",
    "typescript": "^5.3.3",
    "typescript-eslint": "^8.52.0"
  },
  "imports": {
    "#/*": "./*",
    "@hubspot/ui-extensions/*": "node_modules/@hubspot/ui-extensions/dist/*"
  },
  "scripts": {
    "intlayer:test": "npm run ts:patch && (intlayer build && intlayer content test; npm run ts:unpatch)",
    "lint": "eslint .",
    "lint:fix": "eslint . --fix"
  }
}

This may matter because the root package has @hubspot/cli only, while the actual UI extension package already has its own ESLint and React/UI-extension dependencies under src/app/cards.

[joe-yeager]

Thanks for the bug report @luxferre - I will look into it and get back to you.

[joe-yeager]

I was able to reproduce this issue and I have a patch PR for it internally. It should go out as a part of the next release and I will post an update here once it has been resolved.