Expo logo
Expo
Create
Roadmap
Feedback
Feature Requests
Voters
Powered by Canny
type: fingerprint workflow job doesn't support NPM_TOKEN pre-processing for private registries (unlike type: build)
r
rhettwalker86@gmail.com
April 14, 2026
Stanisław Chmiela
Hey rhettwalker86@gmail.com!
How are you passing in the
NPM_TOKEN
? I do see an
eas/use_npm_token
function encoded in the fingerprint job definition before
eas/install_node_modules
which should detect and save to
.npmrc
. You mentioned "our preinstall hook", where/how do you set this?
Care to share a link to a workflow run?
Thanks!
Stanley
·
A day ago
·
Reply
r
rhettwalker86@gmail.com
Summary
type: build in EAS Workflows has built-in NPM_TOKEN pre-processing that writes .npmrc auth before yarn install runs. type: fingerprint does not, making it unusable with private npm registries.
Environment
EAS CLI: latest
Package manager: Yarn 1.22.22 (Classic)
Private registry: AWS CodeArtifact (scoped @orion packages)
Current behavior
When using type: fingerprint with env: { NPM_TOKEN: ... }:
1.) EAS starts Yarn, which loads .npmrc into memory at startup
2.) Our preinstall hook writes NPM_TOKEN to .npmrc on disk — but Yarn 1 already cached config
3.) yarn install fails with 401 Unauthorized on the private registry
4.) Fingerprint computation never completes
Expected behavior
type: fingerprint should write .npmrc auth before starting yarn install, the same way type: build does. See Private npm packages docs.
·
April 14, 2026
·
Reply
r
rhettwalker86@gmail.com
Summary
type: build in EAS Workflows has built-in NPM_TOKEN pre-processing that writes .npmrc auth before yarn install runs. type: fingerprint does not, making it unusable with private npm registries.
Environment
EAS CLI: latest
Package manager: Yarn 1.22.22 (Classic)
Private registry: AWS CodeArtifact (scoped @orion packages)
Current behavior
When using type: fingerprint with env: { NPM_TOKEN: ... }:
1.) EAS starts Yarn, which loads .npmrc into memory at startup
2.) Our preinstall hook writes NPM_TOKEN to .npmrc on disk — but Yarn 1 already cached config
3.) yarn install fails with 401 Unauthorized on the private registry
4.) Fingerprint computation never completes
Expected behavior
type: fingerprint should write .npmrc auth before starting yarn install, the same way type: build does. See Private npm packages docs.
·
April 14, 2026
·
Reply
Powered by Canny