You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However now with this plugin, I run into an error that says next is not installed on the prebuild by the plugin, which runs before my custom prebuild which installs the packages.
Also, this might be better categorized as a feature request, not entirely sure which it falls under exactly
To Reproduce
Steps to reproduce the behaviour:
Create a next project with pnpm and the below netlify.toml
Push to netlify and build without cache. (I think it worked the first few times for me because it has next cached from yarn before, we just migrated over)
With the new plugin version you can use the workaround, though with one change: instead of --prefix=/dev/null, pass --version as the flag. Of course native pnpm support would be best, but this is the best solution for now
* chore: add middleware-src fixture
* fix: ensure relative import for edge-runtime-webpack file
* chore: test middleware in src dir
* fix: middleware function name
* fix: middleware bundle resolution for non-src builds
* chore: fix function name in test
* fix: middleware bundle import separator
* chore: move turborepo fixture into src and add middleware
* chore: update turborepo test to check for middleware headers
Describe the bug
I am using
pnpm
on a nextjs repository and followed the steps here https://answers.netlify.com/t/using-pnpm-and-pnpm-workspaces/2759 and netlify/build#1633 (comment) this was working fine withnext-on-netlify
However now with this plugin, I run into an error that says
next
is not installed on the prebuild by the plugin, which runs before my custom prebuild which installs the packages.Also, this might be better categorized as a feature request, not entirely sure which it falls under exactly
To Reproduce
Steps to reproduce the behaviour:
next
project withpnpm
and the belownetlify.toml
yarn
before, we just migrated over)This repo can be used to reproduce the bug https://github.com/CryogenicPlanet/netlify-next-prebuild-bug
Expected behaviour
A workaround or suggestion to use
pnpm
with this new plugin would be great or a way to disable the plugins prebuildVersions
If you're using file-based installation
The text was updated successfully, but these errors were encountered: