Home Original page

fix: pass NPM_CONFIG_REGISTRY env variable when bundling functions by laktek · Pull Request #3020 · supabase/cli

@laktek

sweatybridge

@laktek laktek deleted the pass-npm-config-registry-env branch

January 7, 2025 03:30

addniner added a commit to addniner/cli that referenced this pull request

Mar 5, 2026 
The Docker bundler for `functions deploy` only passes
`NPM_CONFIG_REGISTRY` to the container environment. When `.npmrc`
uses \${NPM_AUTH_TOKEN} for private registry authentication, the
variable is not available inside the container, causing 401 errors.

Forward `NPM_AUTH_TOKEN` from the host environment to the Docker
container, following the same pattern established in PR supabase#3020 for
`NPM_CONFIG_REGISTRY`.

Closes supabase#4927

addniner added a commit to addniner/cli that referenced this pull request

Mar 17, 2026 
The Docker bundler for `functions deploy` only passes
`NPM_CONFIG_REGISTRY` to the container environment. When `.npmrc`
uses \${NPM_AUTH_TOKEN} for private registry authentication, the
variable is not available inside the container, causing 401 errors.

Forward `NPM_AUTH_TOKEN` from the host environment to the Docker
container, following the same pattern established in PR supabase#3020 for
`NPM_CONFIG_REGISTRY`.

Closes supabase#4927