Open
Description
This is a (Bug Report / Feature Proposal)
Bug report
Description
Okay, I think i finally sorted this out.
If you create a repository then operate a custom domain on it, it seems that packages you push on it (using the custom domain url) will give a 401 error when pulled later on (through npm install/yarn add)
Additional Data
Removing the "authorizer: authorizerGithub" on the target.default handler will remove auth checking from the lambda function. It seems to work correctly after that.
But well, as a drawback everyone can now install your packages given the registry and name.
- NPM CLI version you are using: npm 5.5.1, yarn 1.3.2
- Serverless version you're using: 1.24.1
- Node version you're using: 8.9.1
Metadata
Metadata
Assignees
Labels
No labels