Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ts_project expects json output path incorrectly for root target #2598

Closed
kwonoj opened this issue Apr 8, 2021 · 1 comment · Fixed by #2602
Closed

ts_project expects json output path incorrectly for root target #2598

kwonoj opened this issue Apr 8, 2021 · 1 comment · Fixed by #2602

Comments

@kwonoj
Copy link
Contributor

kwonoj commented Apr 8, 2021

🐞 bug report

Affected Rule

The issue is caused by the rule: ts_project

Is this a regression?

Yes, the previous version in which this bug was not present was: ....

I do not think so

Description

A clear and concise description of the problem...

ts_projects expects json output trims its file name, such as

// actual json is `package.json`
ERROR: /Users/ojkwon/github/ts_project_test/BUILD.bazel:3:11: output '.ts-out/ackage.json' was not created

This happens when try to build targets under this kind of layout

-- workspace
package.json
BUILD // ts_project target exists here

🔬 Minimal Reproduction

https://github.com/kwonoj/ts_project_test
bazel build //:tsproject-test

I tried to move it under subpath like
https://github.com/kwonoj/ts_project_test/tree/move-working

then it looks like building.

🔥 Exception or Error






🌍 Your Environment

Operating System:

  

  

Output of bazel version:

  
Build label: 4.0.0
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Thu Jan 21 07:38:50 2021 (1611214730)
Build timestamp: 1611214730
Build timestamp as int: 1611214730

  

Rules_nodejs version:

(Please check that you have matching versions between WORKSPACE file and @bazel/* npm packages.)

  
3.2.3 / 3.3.0
  

Anything else relevant?

@kwonoj
Copy link
Contributor Author

kwonoj commented Apr 8, 2021

This could be simple misconfiguration on my end instead of actual bugs, I couldn't find what causes it unfortunately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant