readme: add description of ECMAScript

[unikounio]

Added a description of ECMEScript to the readme and adjust the sample files to match.

Issue

Docs: Add sample code ES Modules format to the examples in the README. · Issue #61 · minimistjs/minimist

[unikounio]

@ljharb @shadowspawn
Thank you both for your thorough reviews. I have made the necessary updates based on your feedback.

[shadowspawn]

Looks good to me

[shadowspawn]

Thanks for working through our various comments @unikounio

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.78%. Comparing base (6715df1) to head (98fe3c8).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #62   +/-   ##
=======================================
  Coverage   98.78%   98.78%           
=======================================
  Files           1        1           
  Lines         165      165           
  Branches       70       70           
=======================================
  Hits          163      163           
  Misses          2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ljharb]

Almost there :-)

[unikounio]

@ljharb
Thank you for the thoughtful suggestion. I have addressed it.

[shadowspawn]

Urk. Failing a couple of lint tests due to using "new" features in the example code (const and modules). To be clear, these would be problems if they were in the actual implementation since we support very old node versions.

My first thought is examples using modern syntax are more appropriate and useful for new users. Is it appropriate to add an override to .eslintrc for the examples folder and allow modern features?

Do you already have a preferred way of approaching this @ljharb ?

[ljharb]

yep! add an "overrides" object for example/** in the root eslintrc, and extend @ljharb/eslint-config/node/latest.

[shadowspawn]

Are you happy to look at this @unikounio , or would you like a hand with the eslint change? (Fairly easy hopefully, but depending on what you already know and what you are interested in learning...)

[unikounio]

@shadowspawn
Thank you for your suggestion. I would like to do this ESLint configuration change. Would it be better to include this change in this PR or would it be more appropriate to create a new PR for this change?

[shadowspawn]

Include in this PR thanks.

[unikounio]

Just pushed the changes to apply the latest ESLint config to the examples directory.
Please take a look when you have a moment. Thanks!

[ljharb]

rebased and squashed to one commit, and fixed formatting (and examples → example in eslintrc)

this LGTM and can be ff-merged once @shadowspawn concurs :-)

[shadowspawn]

LGTM 👍

[unikounio]

Thank you both so much for helping me with this PR!
@ljharb and @shadowspawn, I deeply appreciate your support and the valuable feedback you've provided.
I've learned a lot from this experience and am looking forward to any future opportunities to work together again!