fix: windows max path installer issue resolved. - #2275
Open
neoandmatrix wants to merge 3 commits into
Open
Conversation
neoandmatrix
requested review from
AayushSaini101,
Shurtu-gal and
asyncapi-bot-eve
as code owners
August 8, 2026 14:01
🦋 Changeset detectedLatest commit: 133b310 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.



Description
This PR resolves the Windows installer failure caused by @asyncapi/studio. The package ships a Next.js output: 'standalone' build (build/standalone) containing a deeply-nested .pnpm/next@... dependency tree. These paths exceed Windows' 260-character MAX_PATH limit, so NSIS extraction fails during installation with "Error opening file for writing".
The CLI launches Studio and Preview through the programmatic Next.js server (distDir: 'build', see src/domains/models/Studio.ts:37-47). That server reads from build/ as declared in required-server-files.json and never uses build/standalone. The standalone output is therefore dead weight that only serves to breach the path-length limit.
A pretarball hook removes build/standalone from the pack workspace before the installer is built. Because the hook runs for every pack:* target, it also reduces the size of the macOS and Linux artifacts, with no impact on runtime behavior.
The script was tested on PR #2268 and the resulting artifact was tested on windows 10 system. The installation was successful. Below are screenshots of same.
Resolves #2248 #2239 #1787