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
When running the CLI command top bootstrap a nextjs application, the project produces an issue with running eslint. Specifically, the web vitals extension is not configured correctly in .eslint.json. When the adjustment is made locally, this then produces a lot of lint issues that blocks building the application.
We are working on the code merges in starter apps from master to cli-use branch and accommodating any changes required in CLI.
We will keep you posted here once this is updated.
When running the CLI command top bootstrap a nextjs application, the project produces an issue with running eslint. Specifically, the web vitals extension is not configured correctly in
.eslint.json
. When the adjustment is made locally, this then produces a lot of lint issues that blocks building the application.I noticed this was fixed in the nextjs starter kit project (master branch), though the CLI still seems to build the project with a older revision (cli-use). It's been difficult to track this down int the CLI source code, though see it here: https://github.com/contentstack/cli/blob/f28b829d6c60dcd81db7675f37c90620b312034f/packages/contentstack-bootstrap/src/bootstrap/github/client.ts#L10C1-L11C1
Can
cli-use
branch be updated frommaster
so the latest project is installed with bootstrap?The text was updated successfully, but these errors were encountered: