Philippe Serhal comments

Results 89 comments of


                                            Philippe Serhal

[Bug]: Error: Cannot find module 'next/dist/server/future/route-modules/pages/vendored/contexts/router-context'

Duplicate of #2329.

fix: add text/x-component header to .rsc assets generated at build time, don't use rsc-data edge function when hitting .rsc path directly

Superseded by v5.

feat: add waf bypass header to CDN download function

Superseded by v5.

Clarify using `netlify dev` when importing `@netlify/next` in docs

Superseded by v5. Please feel free to reopen if this is still valid.

Brand new install with 5.14 produces many errors, develop terminates with errors

Looks like this was an issue with node.js 23 which was/is not supported, so I'll close this. Feel free to open new issues if you still have issues.

fix(deps): update dependency ipx to v3

@keanu-a oh, cool. I'd been holding off on this one because it was actually quietly not compatible with our `engines.node` range: https://github.com/unjs/ipx/issues/263. but we recently bumped our range up to...

[Bug]: ISR and next/link Prefetch Cause RSC Page Return Content in self.__next_f.push Function With App Dir on Next.js 14.0.3

Hi @AresTG2612 The team at Netlify have now released the new `v5` Next.js runtime which has support for both pages and app router, on-demand and time-based revalidation, automatic fine-grained cache...

macOS Node 23: "internal-data-bridge" threw an error while running the sourceNodes lifecycle: "length" is outside of buffer bounds

If I'm reading these reports correctly, these are all issues with unsupported Node.js versions. Is that accurate? Can anyone here reproduce this issue with a [supported version of Node.js](https://github.com/gatsbyjs/gatsby/releases/tag/gatsby%405.15.0)? Thanks!

[BUG] Option engine-strict=true is not compatible with --omit=dev

For anyone else landing here, you can work around this by using https://github.com/voxpelli/node-installed-check instead. @wraithgar Is this still a priority? It looks like it's been marked as a P1 for...

Failure toinstall[Bug]:

Sounds like this was resolved quite some time ago, so I'll close this issue. Please feel free to open a new issue if this is still occurring with v5 of...