You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a built-in feature of PowerShell, a message is logged stating how long it to load the PowerShell profiles whenever that time is greater than 500 ms. Unfortunately, this message is written to PowerShell's Error stream, which in turn feeds into the stderr of the process spawned by child_process.spawn. Because stderr is checked when constructing an instance of PowerJS and must empty for this to succeed, it is impossible to create an instance of PowerJS if loading the PowerShell profiles takes longer than 500 ms. For use cases where the profiles are not needed, it would be best to just not load the profiles at all, as mentioned in #8. However, there may be instances where it would be helpful to still load the profile. In these cases, it would be necessary for the message stating profile load times to be ignored when constructing an instance of PowerJS.
The text was updated successfully, but these errors were encountered:
As a built-in feature of PowerShell, a message is logged stating how long it to load the PowerShell profiles whenever that time is greater than 500 ms. Unfortunately, this message is written to PowerShell's
Error stream
, which in turn feeds into thestderr
of the process spawned bychild_process.spawn
. Becausestderr
is checked when constructing an instance ofPowerJS
and must empty for this to succeed, it is impossible to create an instance ofPowerJS
if loading the PowerShell profiles takes longer than 500 ms. For use cases where the profiles are not needed, it would be best to just not load the profiles at all, as mentioned in #8. However, there may be instances where it would be helpful to still load the profile. In these cases, it would be necessary for the message stating profile load times to be ignored when constructing an instance ofPowerJS
.The text was updated successfully, but these errors were encountered: