palette.js | Script for generating colour palettes for use with graphs | Data Visualization library

Are you sure that you installed material-ui/core ?

Can you replace

Try adding a .env file to your root project directory (where you have package.json and node_modules). Then inside .env, add CHOKIDAR_USEPOLLING=true. This just worked for me when I was having issues with hot reloading not working. Apparently the "watcher" requires this setting when working with a VM (like WSL). I found this recommended in the top answer here: React create app hot reload is not always working on linux

As per what you said handleColorClick prop has changed, which is why the components are getting re-rendered. Since you are using functional component and hooks in the component, when the component is getting re-rendered the function handleColorClick is redefined again and the reference is getting changed. That's the reason why the components are getting re-rendered even though you pass unique ids as keys.

In order to avoid that you can use useCallback hook which will help you not to get a new function reference unless there's a change in the dependencies provided to the useCallback hook

It was happening to me too, after git-cloning a repo I had been working in (different computer). Symfony4 project. I had ran yarn install and composer install, then set up db, and then this manifest file error was happening. The way for me to fix it, after a bit of research: run encore to build the assets :-)

It turns out that there was a bug in my server program.

I was sending a 'Connection: Keep-Alive' header, and then closing the connection after sending the file.

I now send a 'Connection: Close' header, and everything works perfectly.

Sorry about that.

Problem is with

Reference @material-ui/core as a regular expression instead of a string. /^\@material\-ui\/core\/.*/ to match all imports that begin with the namespace in question.

(Not intending this to be a full code inclusive answer)

Your greens in the second image, across the top run from a blue green to a yellow green. In practical terms this means the top left green is “0 red, maybe 255 green and 200 blue”. At the other side, in the top right, it’s maybe “200 red, 255 green, 0 blue”. (I would have made these more accurate by using a colour detector but I’m on a phone)

Descending down the rows they’re tending towards black by reducing the r g b values, so for the middle row they might go from rgb 0,127,100 to rgb 100,127,0

Algorithmically, though this might be easier to do by using hsv colours rather than rgb, as the columns across go from some higher hue to a lower hue and the rows downwards tend from a high value to a low value. This would probably be easier to implement than doing the rgb math as you just need to accept a hue that will vary from maybe h+40 to h-40 (from a full wheel of 360) and a matrix (and you probably will need to ask for rows and columns not just 20, otherwise how will you know to output 5x4 or 4x5)