avoid the default is not a function unclear error #438
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 8b53a9a The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
🧪 Prereleases are available for testing 🧪 @cloudflare/next-on-pagesYou can install this latest build in your project with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/5926945543/npm-package-next-on-pages-438@cloudflare/eslint-plugin-next-on-pagesYou can install this latest build in your project with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/5926945543/npm-package-eslint-plugin-next-on-pages-438 |
dario-piotrowicz
force-pushed
the
avoid-default-is-not-a-function-error
branch
from
b13ecd8 to
2724be3
Compare
if there is some issue evaluating a lazy loaded edge function its default export ends up not being a function and that results in an unhelpful error like the following: ``` TypeError: u.default is not a function ``` slightly improve the user experience by catching such error and letting the user know that something went wrong with the edge function's evaluation: ``` Error: An error occurred while evaluating the target edge function (<edge-function-path>) ```
dario-piotrowicz
force-pushed
the
avoid-default-is-not-a-function-error
branch
from
2724be3 to
8b53a9a
Compare
jculvey
approved these changes
Aug 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
if there is some issue evaluating a lazy loaded edge function its default export ends up not being a function and that results in an unhelpful error like the following:
slightly improve the user experience by catching such error and letting the user know that something went wrong with the edge function's evaluation:
This should help slightly clarify errors such as the ones in #420