Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
LOCKFILE FIX
🚨 This needs to be merged immediately and everyone has to delete their current forks/clones and refork them! 🚨
You can't have both a
package-lock.json
file and ayarn.lock
file in the same repository. Ever. Super bad!Although npm and Yarn are both JavaScript package managers, their respective lockfiles pull from different sources (
npm
andyarn
respectively) and therefore can get out of sync. The project needs to pick one source and stick to it so that everyone will have the same exact version of every required package.I adjusted the
README
to reflect the use of npm only because installing Yarn requires an extra step.README
ChangesI linted the entire
README
file's markdown and reworded some lines for clarity/conciseness.I copied the issue on the Hacktoberfest repo to this project's Wiki in an effort to consolidate information. I also linted the markdown for that.
I converted that
CONTRIBUTING.md
link into a relative link. It's a handy shortcut you should check out!If you want to do a deep dive, see GFM (GitHub Flavored Markdown).
Under the "Getting Started" directions, I made the change stated above and also added in a step for installing Node.js if the contributor doesn't have it already. Right now that step is just an empty link. I'm going to create an issue to add this to the Wiki and link it back. I'll finish it up later if no one claims it.
I also added a "More Commands" section that displays the basic scripts that come built into the Next.js application which I found in the documentation that was linked. Thank you! 😁
Type of change
Please delete options that are not relevant.
Checklist: