crystallizeapi/crystallize-cli

Scaffold a Crystallize project via the command line

crystallize-cli's Issues

Downloading boilerplate fails with npm v7

So, I tried running npx @crystallize/cli@latest jespers-sandbox, and went through the wizard/journey. I got this error message:

I am unsure about this error, but the next one I have a suggestion for:

I also ran into an error when trying to install dependencies manually (since I saw there was no node_modules-folder):

I've narrowed it down to the @crystallize/content-transformer package. I used the boilerplate Next.js - Content and commerce that has a dependency on version 7.0.1 of said package. And the package again has a dependency on [email protected]. And since npm version > 6 installs peerDependencies this will make the npm install-command fail, unless you supply the --legacy-peer-deps.

TD;LR

Bump up the version on @crystallize/content-transformer in the Next.js - Content and commerce boilerplate.

I've made a PR for this bump here

Stack Overflow - What does npm install --legacy-peer-deps do exactly? When is it recommended / What's a potential use case?

The automated release is failing 🚨

🚨 The automated release from the beta branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the beta branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Too many re-renders

On attempting to run "npm run dev" I get this error:

$ pnpm run dev

> @crystallize/[email protected] dev F:\projects\crystallize-cli
> node index.js


  ERROR  Too many re-renders. React limits the number of renders to prevent an
        infinite loop.

 node_modules/.pnpm/[email protected][email protected]/node_modules/react-rec
 onciler/cjs/react-reconciler.development.js:6424:17

 6421:
 6422:       if (!(numberOfReRenders < RE_RENDER_LIMIT)) {
 6423:         {
 6424:           throw Error( "Too many re-renders. React limits the number of
      renders to prevent an infinite loop." );
 6425:         }
 6426:       }
 6427:

 -renderWithHo (node_modules/.pnpm/[email protected][email protected]/node_mo
  ks          dules/react-reconciler/cjs/react-reconciler.development.js:6424:1
              7)
 -mountIndeterminateCo (node_modules/.pnpm/[email protected][email protected]
  ponent              /node_modules/react-reconciler/cjs/react-reconciler.devel
                      opment.js:9238:13)
 -beginWor (node_modules/.pnpm/[email protected][email protected]/node_module
          s/react-reconciler/cjs/react-reconciler.development.js:10476:16)
 -Object.invokeGuardedCa (node_modules/.pnpm/[email protected][email protected]
  lbackProd             .2/node_modules/react-reconciler/cjs/react-reconciler.d
                        evelopment.js:12101:10)
 -invokeGuardedCal (node_modules/.pnpm/[email protected][email protected]/nod
  back            e_modules/react-reconciler/cjs/react-reconciler.development.j
                  s:12292:31)
 -beginWork$ (node_modules/.pnpm/[email protected][email protected]/node_modu
            les/react-reconciler/cjs/react-reconciler.development.js:16531:7)
 -performUnitOfW (node_modules/.pnpm/[email protected][email protected]/node_
  rk            modules/react-reconciler/cjs/react-reconciler.development.js:15
                340:12)
 -workLoopSy (node_modules/.pnpm/[email protected][email protected]/node_modu
  c         les/react-reconciler/cjs/react-reconciler.development.js:15268:5)
 -renderRootSy (node_modules/.pnpm/[email protected][email protected]/node_mo
  c           dules/react-reconciler/cjs/react-reconciler.development.js:15231:
              7)
 -performSyncWorkO (node_modules/.pnpm/[email protected][email protected]/nod
  Root            e_modules/react-reconciler/cjs/react-reconciler.development.j
                  s:14821:18)