But currently we are just running two build tools together. 😞

you mean you want to use Pants also for managing npm dependencies?

Well, there's some rules out there along with a few simple examples of doing that

But we use pantsbuild for our Python/Java/stuff and then we run Yarn/NPM for our frontend UI stuff.

ye we have the same on our side

Yeah ... it seems pants/bazel/buck don't really have a solid supported version for frontend stuff as well.

what can I say :D

probably PRs are more than welcome

Yeah, I wish I had freetiem to do it.

@happy-kitchen-89482 @enough-analyst-54434 @red-balloon-89377 I would really appreciate if you could take a look on my PR to docs :)

I have another question - so let's say that I want to attach my own task to "binary" goal. What's the proper way to get inside execute method of that task some metadata of build e.g. path of project which is built

I mean I execute ./pants binary my/fs/path so how I can find inside execute method that path my/fs/path? Somewhere in context?

Yes, if you are inside the task, somewhere inside

self.context

.

Probably what you want is to poke around

self.context.target_roots

, which has the information about… the target roots

@stocky-account-81383 @chilly-painter-67686 I’m very interested in seeing Yarn support. I’m happy to review any of your PRs! I haven’t written an extension so one of the other maintainers may be more helpful with where to start, but definitely happy to review and help as I can.

cc @strong-garage-46607 , who is currently working on improving pants' javascript support

I’m happy to work with either of you to improve front-end to support in Pants. I’m currently adding source-level dependency for yarn. I would be curious what “extensions” you’d like to add and if some of that stuff can be open sourced

Hi guys, I'm having an issue installing the node plugin. I'm getting this error whenever I try to run my node targets:

error An unexpected error occurred: "EACCES: permission denied, unlink '/Users/paul.yau/Library/Caches/Yarn/npm-imagemin-webpack-plugin-2.2.0-e9c6b3223c979bd50a81c9f8b3741e6f420a54e8/.yarn-metadata.json'".

If I run it with sudo, I get:

error Couldn't find a package.json file in "/Users/paul.yau/Library/Caches/Yarn/npm-Metropolis-0.0.0-813a8382e5821a200486404e535ec7f5cc2a6b03"

Which is probably a dependency issue (that module is a github link to something entirely different from the

npm metropolis

module). But trying to run with sudo in the first place doesn't seem right at all.....

On the other hand, if I copy the source of the node plugin from the contrib folder and setup it up to read from the source, I don't have either of these issues (though I do run into issues with

--changed

)

any ideas?

it should never be run with

sudo

, but i expect that at some point you did run it with sudo

should make sure that your user owns your entire home directory, and then ~never run things with

sudo

nuking that cache would help as well

hmmm yeah that's what I thought, I'll try nuking it again in case I missed anything the first time I tried

hmmmm still the same thing. I nuked

.pants.d

,

~/.cache/pants

, and

~/Library/Caches

, though there was one folder that belongs to root, but Yarn belongs to me

error An unexpected error occurred: "<https://registry.yarnpkg.com/imagemin-webpack-plugin/-/imagemin-webpack-plugin-2.2.0.tgz>: EACCES: permission denied, mkdir '/Users/paul.yau/Library/Caches/Yarn/npm-imagemin-webpack-plugin-2.2.0-e9c6b3223c979bd50a81c9f8b3741e6f420a54e8/dist'".

when I check the module it's complaining about, I do own it, but the permissions are different from other modules somehow.

drwxr-xr-x     6 paul.yau  staff     192 Oct  4 11:26 npm-imagemin-mozjpeg-7.0.0-d926477fc6ef5f3a768a4222f7b2d808d3eba568
drw-rw-rw-     3 paul.yau  staff      96 Jul 27 08:57 npm-imagemin-webpack-plugin-2.2.0-e9c6b3223c979bd50a81c9f8b3741e6f420a54e8

The bottom one is the offending module

and I still don't understand why if I run it from source it works......

This seems to be a unique issue with

imagemin-webpack-plugin

packaging:

$ npm pack imagemin-webpack-plugin@2.2.0
...
imagemin-webpack-plugin-2.2.0.tgz
$ mkdir /tmp/imagemin-webpack-plugin-2.2.0
$ tar -xzf imagemin-webpack-plugin-2.2.0.tgz -C /tmp/imagemin-webpack-plugin-2.2.0/
tar: package/dist/helpers.js: Cannot open: Permission denied
tar: package/dist/helpers.js.map: Cannot open: Permission denied
tar: package/dist/index.js: Cannot open: Permission denied
tar: package/dist/index.js.map: Cannot open: Permission denied
tar: package/src/helpers.js: Cannot open: Permission denied
tar: package/src/index.js: Cannot open: Permission denied
tar: Exiting with failure status due to previous errors
$ ls -l /tmp/imagemin-webpack-plugin-2.2.0/
total 0
drw-r--r-- 4 jsirois jsirois 140 Jul 27 11:57 package

Whereas:

$ npm pack imagemin-mozjpeg@7.0.0
...
imagemin-mozjpeg-7.0.0.tgz
$ mkdir /tmp/imagemin-mozjpeg-7.0.0
$ tar -xzf imagemin-mozjpeg-7.0.0.tgz -C /tmp/imagemin-mozjpeg-7.0.0
$ ls -l /tmp/imagemin-mozjpeg-7.0.0
total 0
drwxr-xr-x 2 jsirois jsirois 120 Oct  4 14:49 package

And ditto for

npm pack webpack

as one other random sample.

huh. Any ideas of workaround besides downloading the source of that package and try to use it?