CLI to build and develop Next.js apps for Cloudflare Pages
MIT License
Bot releases are visible (Hide)
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
has
entries in the build output config not applying to route destination paths.process.env
not being enumerable due to being a proxy.Published by github-actions[bot] about 1 year ago
next/cache
data revalidation.cb32baf: avoid the default is not a function unclear error
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>)
291bfde: Stop the cache
property in fetch requests causing internal server error.
4570aa6: add vercel@31 as a peer dependency
c788def: fix package version detection for yarn
fe6ea04: Add vercel@32 as a peer dependency
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
7da1fd8: fix package version detection not correctly working with yarn v1
5bfbbe1: Add workaround so that people can use standard not-found routes in their app directory applications
The problem is that:
The workaround being introduced here is:
Besides the above the no-app-not-found-runtime
eslint rule has been introduced to try to help developers avoid
the issue
7f94fd2: Apply search params to rewritten URLs in matching.
7da1fd8: install vercel yarn dev dependency only when not already present
Published by github-actions[bot] about 1 year ago
5bfbbe1: Add workaround so that people can use standard not-found routes in their app directory applications
The problem is that:
The workaround being introduced here is:
Besides the above the no-app-not-found-runtime
eslint rule has been introduced to try to help developers avoid
the issue
Published by github-actions[bot] about 1 year ago
_routes.json
file in the root of the project. Entries in the root's file are copied over to the generated one in the output directory.3affd17: Normalize injected import paths for builds done on Windows machines.
226d562: Specify the framework
is nextjs
in the Vercel project.json
file.
5aefce5: watch mode only on file changes
only watch for file changes instead of watching for all possible changes (such as directories additions/removals, etc...),
making sure that we don't rerun the build process unnecessarily
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
660ed5e: Optimize build output function processing to increase next-on-pages' build speed by 2-4x.
11afe0a: Group code block identifiers by the function files that they are consumed in. This reduces the total number of unique files created for identifiers that are used in multiple functions, like Webpack chunks or manifests.
ee6b7dc: add user-agent header to outgoing fetch requests
mimic Next.js' behavior of setting (if not already present) a user-agent
header set to Next.js Middleware
see: https://github.com/vercel/next.js/blob/6705c803021d3bdea7fec20e5d98f6899e49836d/packages/next/src/server/web/sandbox/context.ts#L318-L320
this helps making next-on-pages more consistent with Next.js on Vercel
(it and can solve issues in which such header is necessary, as for example when making Github rest api calls,
see: https://github.com/cloudflare/next-on-pages/issues/376#issuecomment-1628416988)
next.config.js
rewrites unintentionally redirecting the user instead of rewriting the request./_next/static
exclusion in _routes.json
being incorrect when the directory is not in the root.Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] over 1 year ago
619beea: bundle assets produced by the Vercel build and make them accessible via fetch
Vercel/Next can allow access binary assets bundled with their edge functions in the following manner:
const font = fetch(new URL('../../assets/asset-x', import.meta.url)).then(
(res) => res.arrayBuffer(),
);
As you can see in this @vercel/og
example:
https://vercel.com/docs/concepts/functions/edge-functions/og-image-generation/og-image-examples#using-a-custom-font
This sort of access to bindings is necessary for the @vercel/og
package to work and might be used in other packages
as well, so it is something that we need to support.
We do so by making sure that we properly bind the assets found in the Vercel build output into our worker
and that fetches to such assets (using blob urls) are correctly handled (this requires us to patch the global fetch
function)
76a8bb4: Fix multiple search params with the same key not being preserved
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
f1f5a95: remove eslint missing-image-loader
rule
the missing-image-loader
rule is no longer needed since @cloudflare/next-on-pages
version 1.3.0 as basic support for the Image
component has been introduced
(in the following PR: https://github.com/cloudflare/next-on-pages/pull/357), therefore there isn't
a real need to warn developers not to use the Image
component without a custom loader
(since the component will just work by default).
Warning
This is technically a breaking change to theeslint-plugin-next-on-pages
package
since linting would break for users specifically including themissing-image-loader
rule (causingDefinition for rule 'next-on-pages/missing-loader' was not found
errors)
however currently we don't assume that many people are using the plugin with the rule
specifically included, moreover the resolution for the breaking change is to simply
remove the rule from the application's eslint configuration so it is also extremely
simple to fix, thus we didn't consider this worth a major bump
Published by github-actions[bot] over 1 year ago
--outdir
flag.f879ffd: Prevent middleware redirects applying search params.
When a middleware function results in a redirect, the location header specified in the response is the full destination, including any search params, as written by the developer. Previously, we always applied search params to redirects found during the routing process, no matter what. This meant that we accidentally were applying search params to middleware redirects, which would alter the intended final destination. This change prevents that from happening.
3a95489: Fix middleware returning new NextResponse
resulting in 404 for routes that don't exist in the build output.
2dceb75: Fix middleware being invoked multiple times in a phase during routing when there is more than one config entry.
Published by github-actions[bot] over 1 year ago
daa32fd: update no-unsupported-config rules (to match the latest supported configs table)
c21c995: add fallback detection check in no-unsupported-configs rule
add an additional check in the no-unsupported-configs rule so that if the rule
were to fail detecting the config's name as a last resort we fall back checking
the variable declaration present just after the "/*_ @type {import('next').NextConfig} _/"
comment
Published by github-actions[bot] over 1 year ago
b1c3a33: fix --info showing [object Promise] for relevant packages instead of their versions
a9b8c3c: Overwrite prerendered files if they already exist in the output directory.
When using --skip-build
, it would fail if a prerendered file already existed, so we need to override the files so that the build process can continue like normal. This was problematic as after the first build, the prerendered files would now exist in the output directory as static assets, preventing any additional builds.
b1c3a33: fix vercel command not found issue