Closed lloydk closed 1 week ago
Name | Link |
---|---|
Latest commit | a7e94faaf2a4a3090eb189508d810854e9bc1f67 |
Latest deploy log | https://app.netlify.com/sites/colorjs/deploys/667d9e9fc28bdc000832edac |
Deploy Preview | https://deploy-preview-571--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.
I'm confused as to why there are so many dtslint errors in CI. I cloned this repository into a new directory, did an npm install added the changes in this PR ran npm run lint:ci
and got a different set of dtslint errors (errors fixed by #569).
Due to typescript errors in the code base the
tsc
portion ofbuild:ts
is hardcoded to always return a 0 exit code.This should work on Linux and Mac (I only tested it on Linux). If we want to support building on Windows then we need a different strategy for the exit code. There are a number of npm packages that will handle the exit code in a cross platform manner. (e.g. https://github.com/kachkaev/suppress-exit-code).