Estou seguindo o tutorial Creating a new section , porém, ao rodar o comando faststore cms-sync recebo um erro no final da execução (imagem em anexo) e a minha seção não aparece no CMS.
Fala @allyssonalmeida , tudo bem? Você está fazendo uso do nvm p/ gerenciar as versões do node? Se sim, passamos por esse problema recentemente também.
Essas duas issues nos ajudaram compreender o problema e soluciona-lo.
opened 04:30AM - 14 Jan 22 UTC
closed 05:49AM - 28 Jan 22 UTC
Release 8.x
Bug
### Is there an existing issue for this?
- [X] I have searched the existing i… ssues
### This issue exists in the latest npm version
- [X] I am using the latest npm
### Current Behavior
I have updated to the latest npm v8.3.1 and it is showing me an error while using the command "npm outdated -g --depth=0". See the image; https://imgur.com/a/5fMZlye. It was fine on v8.3.0. What is the solution?
### Expected Behavior
It should return the outdated packages after a successful run. But it is giving error.
### Steps To Reproduce
1. In this environment...
2. With this config...
3. Run '...'
4. See error...
I am using Windows 10 (Enterprise - Latest Version). I have the latest node and npm installed at the moment.
### Environment
- npm:
- Node.js:
- OS Name:
- System Model Name:
- npm config:
```ini
; copy and paste output from `npm config ls` here
```
; "user" config from C:\Users\Bilal\.npmrc
registry = "http://registry.npmjs.org/"
; node bin location = C:\Program Files\nodejs\node.exe
; cwd = C:\Users\Bilal
; HOME = C:\Users\Bilal
; Run `npm config ls -l` to show all defaults.
npm ERR! Unexpected token '.' with with nvm-windows <= 1.1.7 · Issue #4234 · npm/cli · GitHub (caminho p/ solução)
