Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't Deploy with v9 & Now 2.0 #8052

Closed
Pushplaybang opened this issue Jul 22, 2019 · 3 comments
Closed

Can't Deploy with v9 & Now 2.0 #8052

Pushplaybang opened this issue Jul 22, 2019 · 3 comments

Comments

@Pushplaybang
Copy link

Pushplaybang commented Jul 22, 2019

Bug report

Since upgrading to v9 I've run into several issues that stop the deployment, the app runs fine with now dev . This includes

  • can't load grpc
  • self register bug
    • both avoided when setting grpc to external in custom webpack config as mentioned
  • can't use latest firebase - produces pages/about.js:29:31) code: 'MODULE_NOT_FOUND' } when that page clearly exists, (downgrading to 5.11.1 "solves" this)

Seems to relate to #7894 #7758 #6655

Working around the above I now get the following as mentioned here #7894 (comment)

running "yarn run now-build"
Jul 22 2019 14:05:48:345 | ...next.config.js | yarn run v1.16.0
Jul 22 2019 14:05:48:403 | ...next.config.js | $ next build
Jul 22 2019 14:05:49:159 | ...next.config.js | Creating an optimized production build ...
Jul 22 2019 14:05:49:824 | ...next.config.js | > Using external babel configuration
Jul 22 2019 14:05:49:824 | ...next.config.js | > Location: "/tmp/bc0fa1c/babel.config.js"
Jul 22 2019 14:07:52:235 | ...next.config.js | Failed to compile.
Jul 22 2019 14:07:52:235 | ...next.config.js | ./node_modules/amp-toolbox-optimizer/lib/transformers/AddBlurryImagePlaceholders.js
Jul 22 2019 14:07:52:235 | ...next.config.js | Module not found: Can't resolve 'jimp' in '/tmp/bc0fa1c/node_modules/amp-toolbox-optimizer/lib/transformers'
Jul 22 2019 14:07:52:235 | ...next.config.js |  

To Reproduce

Attempt to deploy nextjs v9 with firebase

Expected behavior

Can deploy next js v9 to Now 2.0

@timneutkens timneutkens changed the title Can't Deploy with v9 & NOW 2.0 Can't Deploy with v9 & Now 2.0 Jul 22, 2019
@Timer
Copy link
Member

Timer commented Jul 22, 2019

Hey @Pushplaybang!

Thanks for opening this issue, but I'm going to close it as a duplicate of some of the linked issues.

In this case, you're being primarily affected by #7758 -- please subscribe to that issue for updates.

Thanks!

@Timer Timer closed this as completed Jul 22, 2019
@Pushplaybang
Copy link
Author

@Timer thanks, I appreciate the link, I thought it may be useful to bring these together, as I seemed to be darting around the issues attempting to find the right one, and thought it may be useful.

@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants