Hi Hubert, One cause for the issue you are having could be globally installed (or otherwise reachable via your module search path) node modules that conflict with those in our packaged yarnpkg.
Is NODE_PATH set ? If you try: npm root -g it should return /usr/local/lib/node_modules And: ls -l /usr/local/lib/node_modules should be empty. Besides these checks, to help us pinpoint the problem, can you please try to repeat the procedure with debug information turned on for all modules like this: NODE_DEBUG=* yarnpkg add leftpad &> log and attach the log to this bug. Another option would be to debug the JS execution with chromium inspector: https://nodejs.org/en/docs/guides/debugging-getting-started/ launching yarnpkg lile this: node --inspect /usr/bin/yarnpkg ... and look for what code it is executing when it encounters the EINVAL error. Let us know ! Paolo
