feat(next): Update to next 9.3.1

[Jule-]

Integrate Next.js breaking changes

Add package-lock.json into source control (if you do not understand the usefulness of this file I recommend that you read this npm-package-lock.json).
=> while it is useful for apps it becomes irrelevant for packages since ignored by npm in dependency trees. Committing it could hide issues that third party could have when adding this package as new dependency since it will install last versions of dependencies following semver rules.

Checklist

• run npm run test
• tests are included (unchanged)
• documentation is changed or added (no need)
• commit message and code follows Code of conduct

[tmayr]

Will this be merged at some point Anything we can do to speed it up?

[simonecorsi]

Hey, thanks for the fixes! Any chances on advancing this PR? Is there some help needed ? I'm using your fixes as a monkey patch and would be cool having it merged 😄

If the problem is the package-lock maybe you can move in a separate issue so you both can discuss it separately!

[Jule-]

@Kirkhammetz Yes sorry it runs out of my mind, thanks for the ping, push incoming. 😉

[Jule-]

@mcollina anything else or it is good for you?

[mcollina]

This still need the removal of package-lock, thanks.

[Jule-]

🤦 omg... No comment. 😅

[Jule-]

Hum I am confused with Travis error log, does it seems relevant to you? Or it is purely CI issue?

{ Error: EEXIST: file already exists, mkdir '/home/travis/build/fastify/fastify-nextjs/.next'
  errno: -17,
  code: 'EEXIST',
  syscall: 'mkdir',
  path: '/home/travis/build/fastify/fastify-nextjs/.next' }

[Jule-]

Well the reason is because Next.js requirements is NodeJS 10.13 or later.
https://nextjs.org/docs#system-requirements

Related issue: vercel/next.js#11601

@mcollina Want me to patch .travis.yml by removing all build tests under this version?

[mcollina]

Want me to patch .travis.yml by removing all build tests under this version?

Please do, thx

[mcollina]

lgtm