You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I planned to use the typescript test workspace to learn about latest practices for bazel+typescript+grpc.
I noticed it is using ts_library but had read that ts_project is preferred for new code so I was going to try converting.
But before I got to that...
I changed nodejs_test to nodejs_binary and ran bazel run //:test_main. All good.
I wanted to know how the import path was resolving (js_lib/js_lib_pb/demo_pb). I added a line to console.log(demo_pb) and could no longer run without getting an error: Cannot find module 'js_lib/js_lib_pb_demo_pb.js. Seems like the import can get past the typescript compiler but the lib js isn't actually resolved at runtime?
Also, I was wondering how IDE (e.g. VS Code) is supposed to know how to resolve the imports.
The text was updated successfully, but these errors were encountered:
Description
I planned to use the typescript test workspace to learn about latest practices for bazel+typescript+grpc.
I noticed it is using
ts_library
but had read thatts_project
is preferred for new code so I was going to try converting.But before I got to that...
I changed
nodejs_test
tonodejs_binary
and ranbazel run //:test_main
. All good.I wanted to know how the import path was resolving (
js_lib/js_lib_pb/demo_pb
). I added a line toconsole.log(demo_pb)
and could no longer run without getting an error:Cannot find module 'js_lib/js_lib_pb_demo_pb.js
. Seems like theimport
can get past the typescript compiler but the lib js isn't actually resolved at runtime?Also, I was wondering how IDE (e.g. VS Code) is supposed to know how to resolve the imports.
The text was updated successfully, but these errors were encountered: