microsoft / microsoft/lage

v2: no targets found that matches the given scope.

Open
#577 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
816
Forks
88
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

I upgraded https://github.com/exceptionless/Exceptionless.JavaScript from latest 1.9.x to 2.0.0 and now when I run

npm run build

> @exceptionless/monorepo@2.0.0-dev build
> lage build --no-cache --verbose --no-deps

lage: no targets found that matches the given scope.

To Reproduce
Steps to reproduce the behavior:

  1. Clone https://github.com/exceptionless/Exceptionless.JavaScript
  2. Upgrade lage to latest release and npm install
  3. run npm run build
  4. See error

Expected behavior
It should build all the projects.

Environment/Troubleshooting

  System:
    OS: Windows 10 10.0.22621
    CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
    Memory: 17.10 GB / 31.92 GB
  Binaries:
    Node: 19.6.0 - C:\Program Files\nodejs\node.EXE
    npm: 7.22.0 - ~\AppData\Roaming\npm\npm.CMD
  Managers:
    pip3: 22.3 - C:\Python311\Scripts\pip3.EXE
  Utilities:
    Git: 2.39.1.
    FFmpeg: 5.1.2 - C:\ProgramData\chocolatey\bin\ffmpeg.EXE        
  Virtualization:
    Docker: 20.10.21 - C:\Program Files\Docker\Docker\resources\bin\docker.EXE
  IDEs:
    VSCode: 1.75.0 - C:\Users\blake\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD
    Visual Studio: 17.5.33318.248 (Visual Studio Community 2022)    
  Languages:
    Java: javac 16
    Python: 3.11.0
  Databases:
    SQLite: 3.32.2 - C:\Android\android-sdk\platform-tools\sqlite3.EXE
  Browsers:
    Edge: Spartan (44.22621.1194.0), Chromium (109.0.1518.70)       
    Internet Explorer: 11.0.22621.1

If this is an issue with run order of tasks, please paste in the result of lage info [your command(s)] [options]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by cloning the repository, upgrading lage, installing dependencies, and reproducing the failure with npm run build. Use lage info with the build command to inspect target discovery and task scope; done means the command builds all projects without reporting that no targets match.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
build-system, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.