Add color spaces for HSLuv and HPLuv

[lloydk]

Add color spaces for HSLuv and HPLuv.

The conversion routines where adapted from the typescript source code in the HSLuv repository.

Tests

The HSLuv repository has test data in json format.

I added a script to generate tests suites for hpluv and hsluv. npm run test:generate-hsluv will create test/hpluv.js and test/hsluv.js. The tests take forever to load/run on my ancient Windows PC when run via npm run test. Running the individual test files is less bad. I've added the files to .gitignore so they aren't committed accidently.

In Gamut Tests

I added a test suite for inGamut() and the various methods of specifying the gamutSpace for a color space. HSLuv has a gamutSpace of srgb and HPLuv has a gamutSpace of "self".

Closes #339, closes #284

[netlify]

✅ Deploy Preview for colorjs ready!

Name	Link
🔨 Latest commit	c9a27ac
🔍 Latest deploy log	https://app.netlify.com/sites/colorjs/deploys/65c47cee6674e2000812e216
😎 Deploy Preview	https://deploy-preview-404--colorjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[LeaVerou]

Cool idea to import the tests from that repo!
However, if we're gonna pin it to a specific commit, we may as well just copy the file over and import it in the test. There is however value in loading the latest version of the file. Not sure what route you'd rather go with.

[lloydk]

The test data hasn't changed in 8 years so I guess there's no value in pinning to a specific commit. I don't think the file will ever change and if changes are required a snapshot-rev5.json will be created.

My preference right now would be to do the least amount of work. So either keep it as is or change the testDataUrl to not reference a specific commit.

[lloydk]

Walked the dog and changed my mind.

• I'll create a test/hsluv directory that contains a copy of the json test data and test files for hpluv and hsluv
• the test files will load the json test data and create the appropriate tests
• the test:generate-hsluv script will be deleted
• npm run test:hsluv will run the hsluv tests

[lloydk]

I've revamped the tests:

• no generation step
• all tests and test data are stored in test/hsluv
• npm run test:hsluv to run the tests

[LeaVerou]

I would move test/hsluv/hpluv.js and test/hsluv/hsluv.js to be directly into test (and they can still import the files they need from hsluv/. Other than that, LGTM.

[lloydk]

I would move test/hsluv/hpluv.js and test/hsluv/hsluv.js to be directly into test (and they can still import the files they need from hsluv/. Other than that, LGTM.

Done

[LeaVerou]

Merged, thanks! 🎉