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
Please publish latest version on powershellgallery #260
Comments
I just pushed a new version, but got a warning that suggests #242 may not have been sufficient. Give it a try?
|
It looks like Moving exported functions from |
The warning message should be improved. Using wildcards results in poor performance on V3 and beyond when using module auto-loading (so could be any command). PowerShell has to analyze the script/dll/whatever when you use wildcards, but if you avoid wildcards, PowerShell skips that potentially slow work. So best practice is to use:
Instead of:
|
So can we drop Lines 30 to 48 in 5f8e878
|
By default, all functions, cmdlets, and aliases are exported, so if that's what you're doing, it's not necessary. But if you have have internal functions or aliases, then maintaining the list in both places is unfortunately necessary for the best performance. |
Avoiding wildcards in the manifest improves performance and placates tests. See discussion in dahlbyk#260.
Does this include exporting |
I had a feeling private wouldn't have any effect, but had to test to be sure. And indeed, private functions get exported. That is probably an oversight, but it doesn't help you if it gets fixed, so you should stick with Export-ModuleMember. |
I'd like to clean up the PS Gallery versioning process as part of the push to 1.0: #328 |
I'm closing this since the latest version is posted to the PSGallery. And the current posh-git.psd1 no longer uses |
#224 is still reproducible.
The text was updated successfully, but these errors were encountered: