How to test icons local ?

[adsingh14]

Hi ! I've created an icon but unable to test it locally. I tried both docker and npm way.

Build and test the package using $ npm test
: This command working

Run the project linting process using $ npm run lint
: This command showed several errors after passing icon test.

TL;DR:

In docker,
First command runs, docker build . -t simple-icons create a container successfully
docker run -it --rm --entrypoint "/bin/ash" simple-icons this command doesn't run.

I prefer the npm way but why it creates an error if I followed the rules?

[jorgeamadosoria]

you said you created an icon: which one? did you made a branch or submitted a PR? If you did please send me the link to see if I can reproduce the errors you report.

I'm going to focus on the npm way, and ignore docker for the time being.

[jorgeamadosoria]

Well, your second PR looks good, I already merged it.
You are welcome to keep contributions going, I'm sure if you keep at it you will find the problem that is not letting you run the project.

[adsingh14]

Well, I'm doing 'research' 😅 on this. I'll add more icons and happy to maintain this repo as well.

I will try another ways to run this project locally. May I know which OS you're using?

[jorgeamadosoria]

Currently I'm on MacOS. It's not my system of choice, but it seems to work just fine for the project.

[adsingh14]

Looks like Mac or Linux, both are good for non-Windows development.
I tried to run lint command on 'zsh', still same issue.

Nodejs: v16

[jorgeamadosoria]

my node is 14.15
Windows may be problematic for the command lines, yes.

[ericcornelissen]

@adsingh14 this can indeed be a problem on Windows due to the fact that Windows uses different characters for line-endings than Unix (Linux and Mac) systems. This is enforced to avoid "phantom" changes (where a file has changed in the line-ending it has, which is not visible).

Git for Windows has an option for this that you have to configure correctly for this problem to go away. If I'm not mistaking you can run git config --global core.autocrlf true, possible re-clone this repository, and try again. If that doesn't work, researching this option (core.autocrlf) should point you in the right direction to fix the problem.

[adsingh14]

From recent changes. The CRLF error has resolved! Even it's working fine on 'bash' as well as 'Ubuntu Terminal'.