vercel-builder: Deploys to now fail suddenly.
Originally discussing this issue in spectrum #now -> https://spectrum.chat/zeit/now/nuxt-universal-app-deployment-not-working-anymore~982af2e3-7dd4-4193-bd64-dda884ab6df0
After talking with their team, I was told that it appears to be an issue with now-builder itself.
When comparing my failed deployments, vs. my working deployments from this morning the only difference I can see in my deploys is a single dependancy within nuxt/now-builder.
Working Deploy
@now/node-bridge@1.2.1
Failing Deploy
@now/node-bridge@1.2.2
Did something change recently? I don’t see any major release, or updates to the package in the nuxt/now-builder repo.
I guess a quick fix would be pinning the version in the nuxt/now-builder… I’m asking for clarity on what happened in now/node-bridge though.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 2
- Comments: 20 (10 by maintainers)
Commits related to this issue
- chore: ignore @now/node-bridge as of #66, #67 — committed to nuxt/vercel-builder by pi0 5 years ago
I was just re-deploying a project that has been working and but got this.
error execa@2.0.1: The engine "node" is incompatible with this module. Expected version "^8.12.0 || >=9.7.0". Got "8.10.0"Does anyone else share the same issue? (do let me know if this is a totally different problem that I should open a new issue with. I just think that the issue is related since it may have to do with the recent fix)Thanks @pi0 🙏
I’ll think about it and see if we can add an api for choosing the port. In the meantime,
@now/node-bridge@1.2.1is stable and good to use for production so it will work fine 👌0.14.5 should fix deployments. if assigning random port by now-bridge is now a requirement, we may unsupport proxy module and upgrade.
@unr This builder relies on a private api of
@now/node-bridge, which explains why there wasn’t a major release for it.I created a PR to pin the dependency.
I might have a solution that works for the longer term. I’ll test next week 👍