Skip to content

Conversation

@AmirSa12
Copy link
Member

@AmirSa12 AmirSa12 commented Feb 1, 2026

removing the config file was wrong. adding that again here

@continuous-releases-staging
Copy link

continuous-releases-staging bot commented Feb 1, 2026

  • example-1

  • example-2

    npm i https://c97a46db.stackblitz-cr.pages.dev/stackblitz-labs/pkg.pr.new/pkg-pr-new@449
    
    npm i https://c97a46db.stackblitz-cr.pages.dev/stackblitz-labs/pkg.pr.new/playground-a@449
    
    npm i https://c97a46db.stackblitz-cr.pages.dev/stackblitz-labs/pkg.pr.new/playground-b@449
    

commit: c26bd32

@aprendendofelipe
Copy link
Contributor

@AmirSa12
Copy link
Member Author

AmirSa12 commented Feb 1, 2026

Is this related to this error?

https://github.com/stackblitz-labs/pkg.pr.new/actions/runs/20867689123/job/62126379844?pr=445

In forked repos they fail anyway. But this is related to the run that happened on main after merging the PR.

@Aslemammad Aslemammad merged commit edc7bb9 into main Feb 1, 2026
6 checks passed
@Aslemammad Aslemammad deleted the fix/build branch February 1, 2026 16:02
@aprendendofelipe
Copy link
Contributor

So the issue was this run?

https://github.com/stackblitz-labs/pkg.pr.new/actions/runs/21561629151/job/62126669233

I want to make sure I understand this correctly. From what I can tell, the config plugin is working around an issue caused by hooks in defineNuxtConfig.

Does that interpretation make sense?

If so, would you be open to a PR proposing a more robust solution while preserving the current routing behavior? The current approach seems fragile and potentially prone to breaking with dependency updates.

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.

4 participants