[New practice exercise] Pop count

[Cool-Katt]

Adding pop-count exercise to the js track

[github-actions]

Hello. Thanks for opening a PR on Exercism 🙂

We ask that all changes to Exercism are discussed on our Community Forum before being opened on GitHub. To enforce this, we automatically close all PRs that are submitted. That doesn't mean your PR is rejected but that we want the initial discussion about it to happen on our forum where a wide range of key contributors across the Exercism ecosystem can weigh in.

You can use this link to copy this into a new topic on the forum. If we decide the PR is appropriate, we'll reopen it and continue with it, so please don't delete your local branch.

If you're interested in learning more about this auto-responder, please read this blog post.

---

Note: If this PR has been pre-approved, please link back to this PR on the forum thread and a maintainer or staff member will reopen it.

[IsaacG]

I left comments that may very well be outside the scope of this PR.

There are some checks which are failing.

[IsaacG]

Was this file auto-created? It looks ... wrong. These ought to be in the root ignore file.

[Cool-Katt]

This was an auto-generated file.

[IsaacG]

This is also defined in the root and I suspect isn't needed

[Cool-Katt]

Another auto-generated file.

[IsaacG]

Licensing is done on a repo level, not an exercise level.

[Cool-Katt]

yet another auto-generated file.

[Cool-Katt]

All of the issues that @IsaacG pointed to are with auto-generated files. The command used to get those was ASSIGNMENT=pop-count npx babel-node scripts/sync I think, from the CONTRIBUTING.md. I've not messed with those, as i don't know if they're actually needed.

I also ran through the CI checks and it was all formatting errors. Should be all cleared after the last commit, if you can run them again.

[github-actions]

The "Sync all exercises" action has started running.

[github-actions]

The "Sync all exercises" action has finished running.

[github-actions]

For security reasons, /sync does not trigger CI builds when the PR has been submitted from a fork. If checks were not passing due to code format, trigger a build to make the required checks pass, through one of the following ways:

• Push an empty commit to this branch: git commit --allow-empty -m "Trigger builds".
• Close and reopen the PR.
• Push a regular commit to this branch.

[IsaacG]

@Cool-Katt Do you want to update these?

[Cool-Katt]

You mean to add myself as a contributor? I don't know if I properly understand what you mean.

[IsaacG]

Yup. Or as the author. The only person that worked on this exercise is you so I think it ought to be reflected in the author/contributors docs.

[ErikSchierboom]

Thanks