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

Next.js build failing with final_responder plugin error #333

Open
arunesh90 opened this issue Jan 9, 2021 · 4 comments
Open

Next.js build failing with final_responder plugin error #333

arunesh90 opened this issue Jan 9, 2021 · 4 comments

Comments

@arunesh90
Copy link

I am trying out FAB for the first time to see if I can next.js to work on Cloudflare Workers with it, but I seem to be running to be running into a error that prevents me from testing.

Initiated my test project with create-next-app, then downgraded next to 9.5.5 and also downgraded react and react-dom to the versions that were used at the time for that next.js version.

OS: Windows 10

Versions:
Next.js: 9.5.5
Node.js: 14.15.4

Build logs
$ npm run build && npm run fab:build

> [email protected] build C:\Users\arune\Desktop\Projects\DiscordServers\fab-test
> next build

info  - Creating an optimized production build
warn  - Compiled with warnings

./node_modules/next/dist/next-server/server/load-components.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/load-components.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/require.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/require.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/require.js
Critical dependency: the request of a dependency is an expression

info  - Collecting page data
info  - Finalizing page optimization

Page                                                           Size     First Load JS
┌ ○ /                                                          3.4 kB           63 kB
├   └ css/9c4381274c2a4fd9d205.css                             669 B
├   /_app                                                      0 B            59.6 kB
├ ○ /404                                                       3.44 kB        63.1 kB
└ λ /api/hello                                                 0 B            59.6 kB
+ First Load JS shared by all                                  59.6 kB
  ├ chunks/f6078781a05fe1bcb0902d23dbbb2662c8d200b3.4a36a3.js  11.1 kB
  ├ chunks/framework.1a3cf6.js                                 40.3 kB
  ├ chunks/main.79d6d5.js                                      7.2 kB
  ├ chunks/pages/_app.fc1894.js                                281 B
  ├ chunks/webpack.e06743.js                                   751 B
  └ css/381f5b9c92d1673af027.css                               203 B

λ  (Lambda)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
○  (Static)  automatically rendered as static HTML (uses no initial props)
●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)
   (ISR)     incremental static regeneration (uses revalidate in getStaticProps)

[=== ] info  - Generating static pages (0/2)
> [email protected] fab:build C:\Users\arune\Desktop\Projects\DiscordServers\fab-test
> fab build

       [Builder] � fab build �
       [Builder] Reading plugins from config.
       [Builder] Found the following build-time plugins:
                   @fab/input-nextjs
                   @fab/plugin-render-html
                   @fab/plugin-rewire-assets
       [Builder] and the following runtime plugins:
                   node_modules\@fab\input-nextjs\runtime.js
                   node_modules\@fab\plugin-render-html\runtime.js
                   node_modules\@fab\plugin-rewire-assets\runtime.js
       [Builder] Proceeding with build phase.
       [Builder] Building @fab/input-nextjs:
[@fab/input-ne…] Reading files from C:\Users\arune\Desktop\Projects\DiscordServers\fab-test\.next
[…/input-nextjs] Finding all static HTML pages…
[…/input-nextjs] ✔ Found 2 static html pages.
[…/input-nextjs] Finding all dynamic NextJS entry points
[…/input-nextjs] Found 2 dynamic pages.
[…/input-nextjs] ✔ Wrote C:\Users\arune\Desktop\Projects\DiscordServers\fab-test\.fab\.cache\generated-nextjs-renderers.3b211d2.js
[…/input-nextjs] Finding all static assets
[…/input-nextjs] ✔ Found 14 assets.
[…/input-nextjs] Finding all public files
[…/input-nextjs]   ✔ favicon.ico
[…/input-nextjs]   ✔ vercel.svg
       [Builder] Building @fab/plugin-render-html:
[@fab/plugin-r…] Compiled 2 html files.
[…n-render-html] No fallback injected.
       [Builder] Building @fab/plugin-rewire-assets:
[@fab/plugin-r…] Inlining 9 assets.
[…rewire-assets] ✔ Done.
[…rewire-assets] Generating server code to rewire 7 assets.
[…rewire-assets] ✔ Done.
       [Builder] Build plugins completed in 2.45 seconds.
     [Typecheck] No Typescript plugins detected. Skipping.
      [Compiler] Compiling your server.js:
        [rollup] Error: PLUGIN_ERROR
        [rollup] Stack trace follows:
    Error: "final_responder" does not exist in the hypothetical file system!
    Code: PLUGIN_ERROR
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] fab:build: `fab build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] fab:build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\arune\AppData\Roaming\npm-cache\_logs\2021-01-09T15_32_58_068Z-debug.log
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Reproduction

Attached is a zip with a reproduction project.
To reproduce the above issue, run yarn && yarn build:fab.
fab-test.zip

@arunesh90
Copy link
Author

Interesting... I just tried to reproduce this on my Ubuntu server, and it worked there without issues, so it seems like this only happens on Windows for some reason.

@geelen
Copy link
Contributor

geelen commented Jan 10, 2021

Now that's interesting. Are you using WSL or Node on Windows?

@arunesh90
Copy link
Author

Initially tried with Node on Windows, where I got the above issue.
Tried again last night with WSL2 (Ubuntu 20.04) this time, and that seems to work fine.

@wizzard0
Copy link
Contributor

wizzard0 commented Mar 14, 2021

Reproduces for me on Next 10.0.0.8, node 14.15.4, @fab/cli/1.0.0-rc.9 win32-x64.
Builds fine on WSL2 (not deployable to cfw due to bundle size though...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants