jaysoo
commented
1 year ago I think this is due to the configuration being updated for 15.9. Previously withNx returned the configuration object, but now it returns a function. This is fine if you just exported with module.exports = withNx(config), but if you add other Next.js plugins you will need to do it like this:
// next.config.js
// ...
/**
* @type {import('@nrwl/next/plugins/with-nx').WithNxOptions}
**/
const nextConfig = {
// ...
};
const plugins = [
// Your plugins exlcuding withNx
];
module.exports = async (phase, context) => {
let updatedConfig = plugins.reduce((acc, fn) => fn(acc), nextConfig);
// Apply the async function that `withNx` returns.
updatedConfig = await withNx(updatedConfig)(phase, context);
// If you have plugins that has to be added after Nx you can do that here.
// For example, Sentry needs to be added last.
updatedConfig = require('@sentry/nextjs')(updatedConfig, { silent: true });
return updatedConfig;
};See here for more details:
https://nx.dev/packages/next/documents/next-config-setup#manually-composing-plugins-(nx-15-and-prior)
For Nx 16, we are providing a composePlugins function that will allow the composition to be done correctly.
simonpeters
github-actions[bot]
Current Behavior
when running nx serve or nx build on any project that relies on a nx lib package I get the same error.
Expected Behavior
for the build or serve to work
GitHub Repo
No response
Steps to Reproduce
I have no idea what of my project is causing this issue so its hard to reproduce.
If created new a nx lib and a new nx next project and pasted my old in it to see if it was any boilerplate code but I still have same issues. The issue came up after updating nx but I cannot seem to revert it anymore.
my package.json
Nx Report
Failure Logs
No response
Additional Information
No response