We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When the @next/bundle-analyzer is installed and configured, building the site gives:
../../node_modules/webpack-bundle-analyzer/lib/analyzer.js Module not found: Can't resolve 'fs' https://nextjs.org/docs/messages/module-not-found Import trace for requested module: ../../node_modules/webpack-bundle-analyzer/lib/viewer.js ../../node_modules/webpack-bundle-analyzer/lib/index.js ../../node_modules/@next/bundle-analyzer/index.js ./next.config.js ./src/core/FEAASScripts/FEAASScripts.tsx ./src/Scripts.tsx ./src/Layout.tsx ./src/pages/500.tsx
npx create-sitecore-jss nextjs,nextjs-sxa,nextjs-multisite,nextjs-xmcloud
npm run build
Site should build successfully.
The issue is due to
jss/packages/create-sitecore-jss/src/templates/nextjs-xmcloud/src/components/FEAASScripts.tsx
Line 3 in 8c23ac3
If this import and its usages are commented out, then the error goes away, however of course this will possibly break the FEAAS functionality.
The text was updated successfully, but these errors were encountered:
@mg-aceik Thank you for submitting this ticket! I've added a ticket containing all the details to our internal backlog for thorough review
Sorry, something went wrong.
No branches or pull requests
Describe the Bug
When the @next/bundle-analyzer is installed and configured, building the site gives:
To Reproduce
npx create-sitecore-jss nextjs,nextjs-sxa,nextjs-multisite,nextjs-xmcloud
npm run build
Expected Behavior
Site should build successfully.
Possible Fix
The issue is due to
jss/packages/create-sitecore-jss/src/templates/nextjs-xmcloud/src/components/FEAASScripts.tsx
Line 3 in 8c23ac3
If this import and its usages are commented out, then the error goes away, however of course this will possibly break the FEAAS functionality.
Provide environment information
The text was updated successfully, but these errors were encountered: