generated from salesforcecli/plugin-template
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sm/pr-feedback-doctor #829
Merged
Merged
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,25 +10,23 @@ import { NpmModule } from '../shared/npmCommand.js'; | |
type HookFunction = (options: { doctor: SfDoctor }) => Promise<[void]>; | ||
export const hook: HookFunction = (options) => Promise.all([registryCheck(options)]); | ||
|
||
// eslint-disable-next-line @typescript-eslint/require-await | ||
const registryCheck = async (options: { doctor: SfDoctor }): Promise<void> => { | ||
// find npm install | ||
const npm = new NpmModule(''); | ||
const config = npm.run('config get registry').stdout.trim(); | ||
const customRegistry = | ||
process.env.npm_config_registry ?? process.env.NPM_CONFIG_REGISTRY ?? config !== 'https://registry.npmjs.org/' | ||
? config | ||
: undefined; | ||
// eslint-disable-next-line @typescript-eslint/no-floating-promises | ||
[ | ||
// npm and yarn registries | ||
'https://registry.npmjs.org', | ||
'https://registry.yarnpkg.com', | ||
customRegistry, | ||
] | ||
// incase customRegistry is undefined, prevent printing an extra line | ||
.filter((u) => u) | ||
.map(async (url) => { | ||
await Promise.all( | ||
[ | ||
...new Set([ | ||
// npm and yarn registries | ||
'https://registry.npmjs.org', | ||
'https://registry.yarnpkg.com', | ||
process.env.npm_config_registry ?? | ||
process.env.NPM_CONFIG_REGISTRY ?? | ||
npm.run('config get registry').stdout.trim() | ||
? config | ||
: 'https://registry.npmjs.org', | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. removes the possibility of undefined. the Set handles the duplicate conditional |
||
]), | ||
].map(async (url) => { | ||
try { | ||
const results = npm.ping(url); | ||
|
||
|
@@ -44,5 +42,6 @@ const registryCheck = async (options: { doctor: SfDoctor }): Promise<void> => { | |
`Cannot reach ${url} - potential network configuration error, check proxies, firewalls, environment variables` | ||
); | ||
} | ||
}); | ||
}) | ||
); | ||
}; |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
require-await and floating-promises below are valid errors. that map>async thing shouldn't return until the async calls are done running.