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 13.2 template causes build error "Could not map all functions to an entry in the manifest." #78

Closed
AaronFriel opened this issue Feb 27, 2023 · 7 comments
Labels
question Further information is requested

Comments

@AaronFriel
Copy link

AaronFriel commented Feb 27, 2023

Starting from Next.js 13.2.x (@latest as I write this), the site will fail to build with an error. This is caused by creating a site with:

npx create-next-app@~13.2

Error:

16:08:11.591	⚡️
16:08:11.592	⚡️
16:08:11.592	⚡️ Completed 'npx vercel build'.
16:08:11.593	⚡️
16:08:12.393	⚡️ ERROR: Could not map all functions to an entry in the manifest.
16:08:12.394	⚡️ Please report this at https://github.com/cloudflare/next-on-pages/issues.
@AaronFriel AaronFriel changed the title Next.js 13.2 template causes error "Could not map all functions to an entry in the manifest." Next.js 13.2 template causes build error "Could not map all functions to an entry in the manifest." Feb 27, 2023
@gvatsov
Copy link

gvatsov commented Feb 28, 2023

You could check if it is the same reason and resolution as this one. Cheers!

@mataspetrikas
Copy link

also getting the same error, on a basic config:

const nextConfig = {
  experimental: {
    appDir: true,
    runtime: 'experimental-edge',
  },
};

@n00el
Copy link

n00el commented Mar 16, 2023

You could check if it is the same reason and resolution as this one. Cheers!

Can we forgot this one ticket already? Users getting the same error withouth using the basePath...

@gvatsov
Copy link

gvatsov commented Mar 16, 2023

also getting the same error, on a basic config:

const nextConfig = {
  experimental: {
    appDir: true,
    runtime: 'experimental-edge',
  },
};

Are you getting the error on Windows machine?

@zizifn
Copy link

zizifn commented Mar 16, 2023

My case is this error is in pages build CI, I would say this is 100% reproduce if enable nextjs appDir: true with version 13.2

@dario-piotrowicz
Copy link
Member

@AaronFriel we've made improvements since you've opened the issue and I've deployed various apps using the app dir with 13.2.x, like this one for example: https://simple-pages-dir-1324.pages.dev/

So I think yours is no longer an issue, could you please double check and let me know if you still have any problems with app dir applications using the latest next-on-pages? (PS: remember to set the nodejs_compat flag which is necessary for such apps to run on Pages)

@dario-piotrowicz dario-piotrowicz added the question Further information is requested label Apr 5, 2023
@dario-piotrowicz
Copy link
Member

I'm closing the issue as I haven't yet received a reply to the above comment and suspect that this is no longer an issue

@AaronFriel if you still have some issue with app dir with Next.js 13.2 please feel free to reopen the issue and/or ping me

as well as @mataspetrikas, @gvatsov and @zizifn I hope things are working for you now, if they are not please ping me or open a new issue 🙏

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

No branches or pull requests

7 participants