Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

loleaflet: Bump eslint version to 5.0.0 #369

Closed
mrkara opened this issue Oct 20, 2020 · 1 comment · Fixed by #394
Closed

loleaflet: Bump eslint version to 5.0.0 #369

mrkara opened this issue Oct 20, 2020 · 1 comment · Fixed by #394

Comments

@mrkara
Copy link
Member

mrkara commented Oct 20, 2020

This is an Easy Hack.
Potential mentors: @mrkara

eslint is an npm package for identifying and reporting on patterns found in ECMAScript/JavaScript code and the version we have (3.0.0, specified in loleaflet/package.json) is a bit outdated. So let's update it to 4.0.0 at least for now.

Follow the instructions on the forum to send your first pull request. And consider the instructions below fits into the Do you changes, rebuild & test etc. step.

You need to first, find this line in loleaflet/package.json:

"eslint": "4.18.2"

and change it to look like this:

"eslint": "5.0.0"

Then issue this command so that the new version of the package will be downloaded, along with its dependencies, and a new check on the source code is trigerred:

make clean && make -j `nproc`

The command above might take a few minutes or more depending on the power of your PC. In the meantime, read through the
guide: Migrating to v5.0.0

If the command above gives any errors, fix the errors on the indicated files. (Error messages will tell you the line and column numbers for each error.)

After fixing each file, check the diff to make sure it looks all okay:

git diff

When you are done with all of the listed files, make sure the code builds without errors now:

make clean && make -j `nproc`

Even better, run it, and connect to it via your browser to verify all looks okay:

make run

If you are satisfied with the results. Then commit your changes, push the commit to your forked repo, and create a pull request via web interface. :)

@mrkara
Copy link
Member Author

mrkara commented Oct 21, 2020

Hi @ihristova11, thank you for your interest to contribute. The task is yours. Please feel free to ask any question you may have. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant