Hi! I know better javascript support is coming (is that available in beta somewhere?), but in the meantime, I'm trying to use

experimental_shell_command

to run part of an

npm install

to produce an asset that I need to put into a pex binary. I can't figure out how to get the pex_binary to include the output of the shell command (set with the

outputs

param). I could get it into the docker image separately, but I really do need it in the binary if possible. Is there something simple I'm missing?

I haven't tried this, but I can provide you with a

pnpm

recipe I use right now, maybe it could be of some help?

It looks like I should perhaps try 2.16.x in general over 2.15.x, as shell_command looks to have a lot of improvements

Yep, shell kinda became adhoc tool, which is pretty dope. https://www.pantsbuild.org/v2.16/docs/adhoc-tool

the particular piece that I can't get to work right in 2.15 is around defining resources with those outputs. something like the following:

resources(sources=["*.js", "*.css", "storybook:css:dist/assets/custom-assets.css"], dependencies=["storybook:css"])

I don't get warnings from that syntax, but the resource doesn't look like it is actually defined as expected

I always struggle with this, but should it be a resource or a file?

resource - files are not included in the pex bundle. Although I'm half tempted to convert this to files and bundle this differently, as I know I can get that to work