Skip to content
This repository was archived by the owner on May 10, 2021. It is now read-only.

"blocking" on getStaticPaths' fallback throwing ambiguous error #133

Closed
TejasQ opened this issue Jan 7, 2021 · 1 comment
Closed

"blocking" on getStaticPaths' fallback throwing ambiguous error #133

TejasQ opened this issue Jan 7, 2021 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@TejasQ
Copy link

TejasQ commented Jan 7, 2021

Describe the bug
So my netlify site is g2i-pace, and it refuses to build if I want gSP to be blocking. 🤔

image

To Reproduce
Steps to reproduce:

  1. Create a basic page in a NextJS project with fallback: "blocking" in its exported getStaticPaths function
  2. Build it on netlify with next-on-netlify
  3. Cry

Versions

  • Next: 10.0.1
  • next-on-netlify: 2.7.2
@TejasQ TejasQ mentioned this issue Jan 7, 2021
Closed
@lindsaylevine lindsaylevine added the duplicate This issue or pull request already exists label Jan 9, 2021
@lindsaylevine
Copy link
Contributor

hello hello @TejasQ ! thanks for opening and sorry about this :). lol @ step 3. i believe this is the same issue as #111 so i'll mark this as duplicate and close. please track it there! #111 is currently in our next 10 milestone https://github.com/netlify/next-on-netlify/milestone/1 so it's a priority!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TejasQ @lindsaylevine