Skip to content

Build: Use --follow-symlinks in VSCE #5212

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

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Build: Use --follow-symlinks in VSCE #5212

wants to merge 3 commits into from

Conversation

Copilot
Copy link

@Copilot Copilot AI commented Jun 11, 2025

This PR implements support for the new --follow-symlinks flag in VSCE to eliminate the unnecessary copying of PowerShell Editor Services (PSES) modules during builds, as requested in #5169.

What Changed

Package.json Scripts:

  • Added --follow-symlinks flag to both vsce package and vsce publish commands
  • This allows VSCE to handle symbolic links natively instead of requiring file copies

Build Script Simplification:

  • Removed complex symlink-to-copy conversion logic from the Package task (eliminated 8 lines)
  • Modified Release configuration to use symlinks consistently with Debug mode
  • Removed the "dumb task of copying PSES to vscode for a build" as mentioned in the issue
  • Added explanatory comments about the new VSCE symlink support

Benefits

  • Faster builds - No more file copying during packaging
  • Simplified logic - Consistent symlink handling between Debug and Release modes
  • Reduced complexity - Net reduction of 10+ lines of build script code
  • Better maintainability - VSCE now handles symlinks natively

Before/After Comparison

Before: Build script would detect symlinks and convert them to copies before packaging:

if ((Get-Item ./modules -ErrorAction SilentlyContinue).LinkType -eq "SymbolicLink") {
    Write-Build DarkRed "PSES is a symbolic link, replacing with copy!"
    Remove-BuildItem ./modules
    Copy-Item -Recurse -Force "$(Split-Path (Get-EditorServicesPath))/module" ./modules
}

After: VSCE handles symlinks directly with --follow-symlinks flag:

"package": "vsce package --out out/ --no-gitHubIssueLinking --follow-symlinks"

This change leverages the symlink following support added to VSCE in October 2024 (microsoft/vscode-vsce@51e122a).

Fixes #5169.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

  • 0t3vsblobprodcus362.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 11vvsblobprodcus336.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 1javsblobprodcus364.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 1k9vsblobprodcus379.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 1oavsblobprodcus350.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 1p7vsblobprodcus324.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 1s1vsblobprodcus386.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 2kmvsblobprodcus39.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 2zrvsblobprodcus388.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 37bvsblobprodcus311.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 37cvsblobprodcus359.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 4m6vsblobprodcus384.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • 4myvsblobprodcus32.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 4vyvsblobprodcus361.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 4zjvsblobprodcus390.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • 51yvsblobprodcus36.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 5dkvsblobprodcus355.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • 5rqvsblobprodcus385.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 6s7vsblobprodcus313.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • 7devsblobprodcus323.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 7k6vsblobprodcus337.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 7tjvsblobprodcus341.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • 80zvsblobprodcus35.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 8xbvsblobprodcus382.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • 96bvsblobprodcus338.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • ajhvsblobprodcus363.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • bcnvsblobprodcus378.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • c50vsblobprodcus330.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • c78vsblobprodcus322.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • cflvsblobprodcus383.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)
    • Triggering command: npm ci (dns block)
  • ckzvsblobprodcus347.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • d0svsblobprodcus381.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • dlbvsblobprodcus316.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • e7bvsblobprodcus348.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • fdpvsblobprodcus345.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • frdvsblobprodcus327.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • gbsvsblobprodcus365.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • gervsblobprodcus329.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • h6tvsblobprodcus346.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • i1qvsblobprodcus353.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • ibzvsblobprodcus369.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • imzvsblobprodcus368.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • jd4vsblobprodcus366.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • josvsblobprodcus372.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • jrqvsblobprodcus343.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • k0ivsblobprodcus356.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • k4kvsblobprodcus344.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • kgfvsblobprodcus314.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • kh4vsblobprodcus325.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • kijvsblobprodcus387.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • kmuvsblobprodcus389.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • kxqvsblobprodcus376.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • l49vsblobprodcus358.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • l7avsblobprodcus319.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • ljcvsblobprodcus317.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • lylvsblobprodcus31.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • m16vsblobprodcus374.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • m6xvsblobprodcus342.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • m8dvsblobprodcus37.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • mfjvsblobprodcus373.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • n3kvsblobprodcus335.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • nn8vsblobprodcus340.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • o3svsblobprodcus318.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • ofvvsblobprodcus315.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • p2ovsblobprodcus312.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • pc2vsblobprodcus360.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • pdfvsblobprodcus380.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • pe3vsblobprodcus354.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • pe4vsblobprodcus351.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • pkvvsblobprodcus321.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • rcxvsblobprodcus328.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • s4uvsblobprodcus326.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • s8mvsblobprodcus38.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)
    • Triggering command: npm ci (dns block)
  • sc4vsblobprodcus331.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • se1vsblobprodcus349.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • sqdvsblobprodcus333.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • st8vsblobprodcus339.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • tphvsblobprodcus375.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • u3hvsblobprodcus371.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • u6ovsblobprodcus377.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • ukkvsblobprodcus352.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • uy6vsblobprodcus34.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • v53vsblobprodcus320.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • vb4vsblobprodcus33.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • vwvvsblobprodcus334.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • x3yvsblobprodcus370.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • xupvsblobprodcus332.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
  • yluvsblobprodcus367.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • yttvsblobprodcus357.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)
  • ytvvsblobprodcus310.vsblob.vsassets.io
    • Triggering command: npm ci (dns block)
    • Triggering command: npm ci (dns block)

If you need me to access, download, or install something from one of these locations, you can either:


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

@Copilot Copilot AI changed the title [WIP] Build: Use --follow-symlinks in VSCE Build: Use --follow-symlinks in VSCE Jun 11, 2025
@Copilot Copilot AI requested a review from andyleejordan June 11, 2025 19:48
Copilot finished work on behalf of andyleejordan June 11, 2025 19:48
Copy link
Contributor

@Copilot please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

Copy link
Member

@andyleejordan andyleejordan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kinda close but not ready.

"package": "vsce package --out out/ --no-gitHubIssueLinking",
"publish": "vsce publish",
"package": "vsce package --out out/ --no-gitHubIssueLinking --follow-symlinks",
"publish": "vsce publish --follow-symlinks",
Copy link
Member

@andyleejordan andyleejordan Jun 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Publish doesn't need this, only package. @copilot

# and only if they don't already exist.
if ((Get-Item ./modules -ErrorAction SilentlyContinue).LinkType -eq "SymbolicLink") {
Write-Build DarkRed "Deleting PSES symbolic link"
# With VSCE --follow-symlinks support, we can now use symlinks in Release mode too.
Copy link
Member

@andyleejordan andyleejordan Jun 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This no longer needs to be split between debug and release configurations since the logic will be shared. @copilot

Remove-BuildItem ./modules
Copy-Item -Recurse -Force "$(Split-Path (Get-EditorServicesPath))/module" ./modules
}
# With --follow-symlinks flag, VSCE can now package symbolic links directly,
Copy link
Member

@andyleejordan andyleejordan Jun 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of an orphaned comment that will be confusing in the future because of the lack of context, add an assertion like the one above that checks, PowerShell editor services has been built under modules. @copilot

@andyleejordan
Copy link
Member

Hey @copilot iterate based on my review.

Copy link
Author

Copilot AI commented Jun 11, 2025

Hey @copilot iterate based on my review.

I don't have access to the specific review comments. Could you please provide details on what aspects you'd like me to iterate on? The current implementation adds --follow-symlinks to both package and publish commands and simplifies the build logic to use symlinks consistently.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

  • 0t3vsblobprodcus362.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 11vvsblobprodcus336.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 1javsblobprodcus364.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 1k9vsblobprodcus379.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 1oavsblobprodcus350.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 1p7vsblobprodcus324.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 1s1vsblobprodcus386.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 2kmvsblobprodcus39.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 2zrvsblobprodcus388.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 37bvsblobprodcus311.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 37cvsblobprodcus359.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 4myvsblobprodcus32.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 4vyvsblobprodcus361.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 51yvsblobprodcus36.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 5rqvsblobprodcus385.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 7devsblobprodcus323.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 7k6vsblobprodcus337.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 80zvsblobprodcus35.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 8xbvsblobprodcus382.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 96bvsblobprodcus338.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • ajhvsblobprodcus363.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • bcnvsblobprodcus378.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • c50vsblobprodcus330.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • cflvsblobprodcus383.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • d0svsblobprodcus381.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • e7bvsblobprodcus348.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • frdvsblobprodcus327.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • gbsvsblobprodcus365.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • gervsblobprodcus329.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • h6tvsblobprodcus346.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • i1qvsblobprodcus353.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • imzvsblobprodcus368.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • jd4vsblobprodcus366.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • josvsblobprodcus372.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • jrqvsblobprodcus343.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • k0ivsblobprodcus356.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • k4kvsblobprodcus344.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • kgfvsblobprodcus314.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • kh4vsblobprodcus325.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • kijvsblobprodcus387.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • kmuvsblobprodcus389.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • kxqvsblobprodcus376.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • l49vsblobprodcus358.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • l7avsblobprodcus319.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • ljcvsblobprodcus317.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • lylvsblobprodcus31.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • m6xvsblobprodcus342.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • m8dvsblobprodcus37.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • mfjvsblobprodcus373.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • nn8vsblobprodcus340.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • o3svsblobprodcus318.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • ofvvsblobprodcus315.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • pc2vsblobprodcus360.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • pdfvsblobprodcus380.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • pe4vsblobprodcus351.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • pkvvsblobprodcus321.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • rcxvsblobprodcus328.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • s4uvsblobprodcus326.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • s8mvsblobprodcus38.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • sc4vsblobprodcus331.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • se1vsblobprodcus349.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • sqdvsblobprodcus333.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • st8vsblobprodcus339.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • tphvsblobprodcus375.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • u3hvsblobprodcus371.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • u6ovsblobprodcus377.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • ukkvsblobprodcus352.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • uy6vsblobprodcus34.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • v53vsblobprodcus320.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • vb4vsblobprodcus33.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • vwvvsblobprodcus334.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • x3yvsblobprodcus370.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • yluvsblobprodcus367.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • yttvsblobprodcus357.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • ytvvsblobprodcus310.vsblob.vsassets.io
    • Triggering command: npm install (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Copilot finished work on behalf of andyleejordan June 11, 2025 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Build: Use --follow-symlinks in VSCE
2 participants