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

Update to 2018 data #41

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

atomicpages
Copy link

@atomicpages atomicpages commented Jan 2, 2024

Addresses #34 by moving to 2018 data files. In addition to this fix, the year can now be controlled via .env file containing the YEAR environment variable. I tested using 2022 as well and everything appears to be in order. If there's interest I'd be happy to setup semantic-release and other github actions to help automate keeping this project up to date! Let me know 🚀

@@ -1,28 +1,32 @@
#!/bin/bash

rm -rvf *-10m.json
PATH=$PATH:./node_modules/.bin:
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Load $PATH variables from node bin. This ensures the scripts works on any machine after yarn install is run

rm -rvf *-10m.json
PATH=$PATH:./node_modules/.bin:

rm -rvf *-10m.json build
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean build folder as well ✌️

@atomicpages atomicpages changed the title feat: control year via env file Update to 2018 data Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant