Windows - UNC Path Support via npm.ps1 #48471

Activity

1. mribbons

   added

   feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.

   on Jun 16, 2023
2. github-project-automation

   added this to Node.js feature requestson Jun 16, 2023
3. github-project-automation

   moved this to Pending Triage in Node.js feature requestson Jun 16, 2023
4. tniessen

   added

   windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.

   npmIssues and PRs related to the npm client dependency or the npm registry.Issues and PRs related to the npm client dependency or the npm registry.

   on Jun 19, 2023
5. lukekarrys commented on Jun 23, 2023

   

   lukekarrys

   on Jun 23, 2023

   Member

   More actions

   The npm CLI is almost ready to ship PowerShell scripts (ref: npm/cli#6548). When npm ships these, the Node Windows installer should be updated to place those along with the existing *.cmd files.

   My question is how can we ensure that the Windows installer works whether or not the *.ps1 files are present? It would be nice if the commits updating npm and making the Windows installer place the PowerShell scripts didn't need to land at the same time.
6. lukekarrys

   added a commit that references this issue on Jun 24, 2023

   tools: install npm PowerShell scripts on Windows

   ...

   caacd22
7. bnoordhuis commented on Jun 24, 2023

   

   bnoordhuis

   on Jun 24, 2023

   Member

   More actions

   My question is how can we ensure that the Windows installer works whether or not the *.ps1 files are present?

   https://wixtoolset.org/docs/v3/xsd/wix/file/ - I think the answer is "you can't."
8. lukekarrys commented on Jun 24, 2023

   

   lukekarrys

   on Jun 24, 2023

   Member

   More actions

   https://wixtoolset.org/docs/v3/xsd/wix/file/ - I think the answer is "you can't."

   If that's that case, then here is my plan:

   I'll hold off on my Node PR until the scripts have officially landed in npm and that version of npm has landed in Node.

   Once I do make the Node PR, I'll label it appropriately to indicate that it shouldn't be backported to any Node version that doesn't contain the *.ps1 scripts.

   👍React with 👍2Reacted by Ben Noordhuis and Dustin Freeman
9. github-actions commented on Dec 22, 2023

   

   github-actionsbot

   on Dec 22, 2023 – with GitHub Actions

   Contributor

   More actions

   There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.

   For more information on how the project manages feature requests, please consult the feature request management document.
10. github-actions

    added

    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.

    on Dec 22, 2023
11. mribbons commented on Dec 22, 2023

    

    mribbons

    on Dec 22, 2023

    Author

    More actions

    keep-alive
12. github-actions

    removed

    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.

    on Dec 23, 2023
13. nodejs-github-bot

    closed this as completedin #52009on Mar 27, 2024
14. nodejs-github-bot

    added a commit that references this issue on Mar 27, 2024

    tools: install npm PowerShell scripts on Windows

    ...

    4d86020
15. marco-ippolito

    added 2 commits that reference this issue on May 2, 2024

    tools: install npm PowerShell scripts on Windows

    ...

    e7b9ef2

    tools: install npm PowerShell scripts on Windows

    ...

    c39f15c
16. avivkeller

    moved this from Awaiting Triage to Done in Node.js feature requestson Jun 28, 2024
17. avivkeller

    removed this from Node.js feature requestson Sep 13, 2024