GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — CodeQL fails to detect Javascript/Typescript files · Issue #3384 · github/codeql-action

CodeQL fails to detect Javascript/Typescript files #3384

New issue
Copy link
New issue
Copy link
Open
github/codeql
#21121
github/codeql#21121
Open
CodeQL fails to detect Javascript/Typescript files#3384
github/codeql
#21121
Copy link

Description

@jessehouwing
jessehouwing
opened on Jan 5, 2026
Issue body actions

I was trying to get CodeQL running on the following repo:

https://github.com/jessehouwing/azure-pipelines-msbuild-helper-task/tree/a3aeaf4b459f1912ccf4706d0e0c93a16a4d5ed0

But Code QL analysis fails to find any Javascript / Typescript files. Neither in "default mode" nor in "advanced mode".

[2026-01-05 08:48:07] [build-stderr] Only found JavaScript or TypeScript files that were empty or contained syntax errors.

A workflow log can be found here:
https://github.com/jessehouwing/azure-pipelines-msbuild-helper-task/actions/runs/20710231226/job/59448894856

It is unclear from the error message and from the docs why i can't find any files, because there are 2 Typescript files in the repo, but they aren't in the root (which I suspect is causing the issue).

I managed to resolve this by adding a codeql-config.yml and specifying the paths property to include **/*.ts:

https://github.com/jessehouwing/azure-pipelines-msbuild-helper-task/blob/main/.github/codeql/codeql-config.yml

I don't see why I would have to do this. CodeQL should detect **/*.js, **/*.ts and a few other extensions by default if you'd ask me.

Either the docs should clearly specify how do solve this situation (the docs currently do not contain an entry for this specific error message). But it would be even better if the analysis step would pick a decent set of default search options when it can't find a project.json in the root of the repo.

Reacted by Pavel Tsakalidis, Alberto and Nawaphon Isarathanachaikul (黄海财)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.