menu
up-caret
down-caret

ZEIT

Our mission is to make cloud computing as easy and accessible as mobile computing. You can find our Next.js community here.

# Now

Instant global deployments

Trending conversations
Transpiling for es6 modules and node-server?
@deitcher · 5h
503 on deployment
@codelayer · 25d
Do apps on now stay up for a long time without refreshing?
@marc-sloth-eastman · 2h
BRU1 instances are timing out
@helguita · 34d
Are Now Logs Working?
@txemaleon · 22h

First attempt with v2 and failures

Remy Sharp (@remy) · November 13, 2018 at 3:33pm

First attempt with v2 and failures

November 13, 2018 at 3:33pm

I apologise Team Zeit, as I'm a magnet for bugs.

I've just uploaded my very first attempt at v2 release, a simplistic project that I use for my workshops. It took about 5 minutes and it failed.

This is the output: https://gist.github.com/remy/c0569803ce98bf9b3328dc6313f999a2

The logs are under https://next-ffconf2018-workshop-ljk40wl65.now.sh/_logs

It's complaining that it's too large but I can't see how.

Is there anything else I can provide to help debug? (I'm running it again, but already it's taking a long time - way way longer than with the v1 instance API).


November 13, 2018 at 4:43pm

Hey @remy, looks like you may need to add some new course content for v2!

  • reply
  • like

@remy I can't see your logs. They've been made private by default now on v2, so you probably just need to set public to true in now.json

  • reply
  • like

But yes, those lambdas look way too big

  • reply
  • like

Pretty confusing given that the entire instance image is > ▲ Saving deployment image (13.2M)

  • reply
  • like

What's that line from? v1?

  • reply
  • like

Post a new link with public logs and I'll have a look

  • reply
  • like

v1

  • reply
  • like

I'm uploading two public versions - on v1 + v2 I'll post links once it's "done" (or gives up)

  • reply
  • like

was is statically exported in v1? Or dynamic?

  • reply
  • like

I notice latest now is ignoring the .gitignore too

  • reply
  • like

dynamic - with server backend.

  • reply
  • like

currently doing that hanging thing…

  • reply
  • like

(damn, spectrum push notifications are annoying - keep sliding in when I'm on the page, then clicking clears the page and I have scroll down again!)

  • reply
  • like

looks like it's stuck in a loop (sorry - currently treating this spectrum forum like a chat forum…)

  • reply
  • like

---

So, here's the v2 deploy: https://zeit.co/rem/next-ffconf2018-workshop/k7bqj0dcf - completely hosed, all I did was to add v2 and the build option in the [now.json](https://zeit.co/rem/next-ffconf2018-workshop/k7bqj0dcf/source?f=src/now.json) (as per copy/paste docs).

And here's the v1 deploy: https://remyffconf-workshop-fuelaxqukw.now.sh/ - same code base, just no version or build in now.json - works.

  • reply
  • like

Yeah, spectrum notifications suck. No notifications in the app for direct messages.

  • reply
  • like

It's pretty realtime, I've been treating it more like chat as well

  • reply
  • like

@remy have a link to the code?

  • reply
  • like

All in the previous links - I deployed them all as public

  • reply
  • like

Looking now.

  • reply
  • like

Nice on the MDX. One unrelated note already, is that you may want to lazy load next-bundle-analyzer in next.config.js, so that you can move it to devDependencies

  • reply
  • like

Next gives you phase constants, which you can use for a conditional for dev mode

  • reply
  • like

it's only loaded in that initial boot though, right? So it's not a huge concern (but definitely a better practise). (The codebase is for my updated workshop)

  • reply
  • like

But I don't see why it fails so horrendously

  • reply
  • like
Show more messages