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
* create nodejs_image test cases for launcher and launcher_args
add launcher and launcher_args attrs to nodejs_image, and pass them to app_layer
update docs with note about launcher and launcher_args for nodejs_image
add run-bazel-in-docker.sh allowing non-linux platforms to execute repo build and tests
add .idea to .gitignore
Add test for using nodejs_image with launcher arg
* add documentation for run-bazel-in-docker.sh
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -613,11 +613,13 @@ nodejs_image(
613
613
name="nodejs_image",
614
614
entry_point="@your_workspace//path/to:file.js",
615
615
# npm deps will be put into their own layer
616
-
data= [":file.js", "@npm//some-npm-dep"],
616
+
data= [":file.js", "@npm//some-npm-dep"],
617
617
...
618
618
)
619
619
```
620
620
621
+
`nodejs_image` also supports the `launcher` and `launcher_args` attributes which are passed to `container_image` and used to prefix the image's `entry_point`.
622
+
621
623
If you need to modify somehow the container produced by
622
624
`nodejs_image` (e.g., `env`, `symlink`), see note above in
623
625
<ahref=#overview-1>Language Rules Overview</a> about how to do this
0 commit comments