Closed jwang-lilly closed 1 year ago
@JianWang2016,
I've tested the product and the build script works smoothly also the build next is the official command for building a next.js app. Could you please check your product version on the package.json the latest version is v1.3.1.
Cheers, Sajad
This issue is fixed on v1.3.2
Version
1.3.1
Reproduction link
https://www.creative-tim.com/new-issue/nextjs-material-kit-pro
Operating System
macOS monterey version 12.6
Device
macbook pro
Browser & Version
Chrome Version 108.0.5359.124 (Official Build) (x86_64is up to date)
Steps to reproduce
download the kit
./styles/scss/nextjs-material-kit-pro.scss To use Next.js' built-in Sass support, you first need to install
sass
. Runnpm i sass
oryarn add sass
inside your workspace.Learn more: https://nextjs.org/docs/messages/install-sass
Solution
info - Linting and checking validity of types ..warn - No ESLint configuration detected. Run next lint to begin setup info - Linting and checking validity of types
info - Creating an optimized production build
info - Compiled successfully Warning: You have opted-out of Automatic Static Optimization due to
getInitialProps
inpages/_app
. This does not opt-out pages withgetStaticProps
Read more: https://nextjs.org/docs/messages/opt-out-auto-static-optimizationinfo - Collecting page data
Route (pages) Size First Load JS ...
(Server) server-side renders at runtime (uses getInitialProps or getServerSideProps)
Additional comments
I encountered this issue when using "build next", it can be overcome using "npm run build". It is just strange that npm run build actually executes next build.
I am just concerned about the webpack errors.
Please note, I don't have a reproducible example because it is your own code base. I just ordered it and wanted to see if it can build.