Marko Antolić
Marko Antolić
> Thank you. I just fixed it by running `npm install -g [email protected]` Please avoid doing this. As mentioned in the docs (https://github.com/facebook/create-react-app#quick-overview), it is preferred to always run `create-react-app`...
> Of course, you need to uninstall any globally installed CRA version on your machine before trying it with `npx`. > > @marko-hologram the whole point of this issue report...
> > If people would follow the docs initially they wouldn't even have CRA installed globally (since docs suggest you shouldn't have global installs) and would avoid all of these...
> Yet you don't mention how Because I cannot pinpoint which of the possible fixes might apply to them. I'm at least trying to steer them in the right direction...
> I fixed this issue by changing the version of the `npm` I had the `16.11.1` version installed. Using `nvm` I just changed the version to `14.18.1` > > ```...
> Now CRA projects start with npm and not yarn? 🤔 > > CRA now uses the package manager that you used to create the project instead of just defaulting...
Would love this feature. I have an application that I stopped for few days and then pull requests that were already deployed were merged while the application was stopped. This...
If you are using a version of CRA that uses Fast Refresh for hot reload and don't want to switch from official Slate examples that use `useMemo`, you can just...
> ```ts > const [editor] = useState(withReact(createEditor())); > ``` > > @aliak00 this one creates (and throws away) a new instance of the editor on every re-render, which I guess...
> > This is code that we use: > > ```js > > const editorRef = useRef() > > if (!editorRef.current) editorRef.current = withReact(createEditor()) > > const editor = editorRef.current...