Open decepulis opened 9 months ago
+1 - I can reproduce this by importing @sanity/client. I'm seeing this error without Turbo, its happening in a webpack environment
+1. The issue persists on Next 14.0.0. At the moment, @sanity/client is not usable above 13.4
Hey @shuding, any updates on this issue? This issue is blocking us from upgrading to Next.js 13 or 14 and is not resolved in Next 14. We cannot downgrade to <13.4 as we need the permanentRedirect
function that was introduced in a later version.
Experiencing the same issue also on next 13.4.19
. Is there any way to disable the optimisation without having to downgrade?
Any progress? I'm experiencing the same issue with @sanity/client
and nextjs 14.
Same issue with @sanity/client
. Any Updates?
Same issue with @sanity/client and nextjs 14. Would definitely appreciate any updates.
Looks like this is fixed in the latest release of Next. I tested if @sanity/client
and next-sanity
still gave the same error in my repo (they did), and then updated to next@latest
. Now it works with latest sanity clients.
Link to the code that reproduces this issue
https://github.com/decepulis/nextjs-barrel-reproduction
To Reproduce
I created a new turborepo and installed
next@canary
in the example web and docs directories. I then installedrxjs
in the web directory.apps/web/app/page.tsx
has the following import:Current vs. Expected behavior
yarn build
results in the following errors:Here's a full log of the build, filtered by web for clarity
Verify canary release
Provide environment information
Which area(s) are affected? (Select all that apply)
App Router, SWC transpilation
Additional context
next-sanity
, which hasrxjs
as a dependencylodash
anddate-fns
.NEXT-1684