Issue with now dev

[RemiKalbe]

Hi,

Everything works if I use now, but now dev doesn't work.
If __sapper__/build/index.js doesn't exist I get

404: The page could not be found
Code: FILE_NOT_FOUND

But if __sapper__/build/index.js exist I get

events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE :::3000
    at Object._errnoException (util.js:1022:11)
    at _exceptionWithHostPort (util.js:1044:20)
    at Server.setupListenHandle [as _listen2] (net.js:1367:14)
    at listenInCluster (net.js:1408:12)
    at Server.listen (net.js:1492:7)
    at Object.<anonymous> (/private/var/folders/4m/kshkpbbs27s8m77s6kw9v9cw0000gn/T/zeit-fun-f1d67544251ea/launcher.js:39:8)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)

Furthermore, it would be great if we didn't have to manually build and then deploy.

I followed every change in thgh/sapper-template@220307c

[thgh]

I'm not aware of documentation on how to fix this. Trial and error has already taken quite some time, so all help is welcome!

[antony]

Not sure about this particular issue, but it's worth mentioning now dev is lagging significantly behind now's actual infra, so this plugin won't work at all on now dev since it won't yet let you return an object from the build hook.

Basically I would take now dev with an entire bag of salt, this probably isn't a bug.

[uunomee]

Please see if now.json is close to the readme helps
`Example now.json

{
"version": 2,
"builds": [
{ "src": "package.json", "use": "now-sapper" }
],
}`

[antony]

Just to re-iterate, as of building this, because of the embedded routes in the builder payload, this doesn't work with now dev. Hopefully zeit will update now dev soon, to support their newer build output signatures.

On Sat, 28 Sep 2019 at 14:21, Uuno Mee ***@***.***> wrote: Please see if now.json is close to the readme <https://github.com/thgh/now-sapper> helps `Example now.json { "version": 2, "builds": [ { "src": "*package.json*", "use": "now-sapper" } ], }` — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABVORKJHG7KWQCDULT6OH3QL5K6RANCNFSM4IJXFK6A> .

--

…

________________________________ ꜽ . antony jones . http://www.enzy.org

[antony]

Closing this as it relates to shortcomings in now dev rather than in this project.

[zolotokrylin]

Hi everyone 👋
So we are not being able to reproduce the environment of the serverless functions locally?
Is there any workaround that will allow us to simulate functions locally? Otherway it is becoming very uncomfortable to develop locally.

[thgh]

Thinking realistically, now dev will never support Sapper. OTOH if you restart your server every 5 minutes, you are pretty much there, no?

[jorngeorg]

Should this be flagged higher up in the readme? I suspect it's a deal breaker for many.

[DougAnderson444]

I run vercel dev with sapper and don't seem to have any issues. But I haven't applied this builder yet...

The only work around I need to do is delete the __sapper__/dev folder manually before I run dev.

[jorngeorg]

vercel dev is working for me now. Currently using Vercel CLI 20.1.0