Thank you for your first contribution! 🎉

🔔 @capipo you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

You can expect an initial review within five business days.

Could you check this @capipo

Hi @pernielsentikaer.

I'm passing process.env because I need to support the PASSWORD_STORE_DIR environment variable, and potentially other variables supported by the pass command.

Perhaps if you filter out variables that start with PASSWORD_STORE we could continue to support those variables and your problem would be solved.

Nevermind, I see that that variable is passed later

Hi @capipo,

I'm not really sure about that since the extension is overwriting the PASSWORD_STORE_DIR env variable. So either way, it would not use the env variable from process.env

export async function pass(cmd: string, storeDir: string = ''): Promise<string> {
  const passCmd = `pass ${cmd}`;
  const { stdout, stderr } = await execAsync(passCmd, {
    timeout: 10000,
    env: {
     ...process.env
      PATH: await envPath(),
      PASSWORD_STORE_DIR: storeDir,
    },
  });

  if (stderr) {
    throw new Error(stderr);
  }
  return stdout;
}

Let me try removing the locale issue and fix this since maybe it can have conflicts with other peoples custom variables since PASSWORD_STORE_DIR is not the only env var used by pass

@capipo pls check the above solution 👆🏽

@pernielsentikaer I think this can be merged

Published to the Raycast Store:
https://raycast.com/capipo/pass

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.