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

Dev #13

Closed
wants to merge 23 commits into from
Closed

Dev #13

wants to merge 23 commits into from

Conversation

hvj7
Copy link
Contributor

@hvj7 hvj7 commented Feb 12, 2020

Updated package-json.lock to latest version

@Kushagra-0801
Copy link
Contributor

Bro! WTF!?

@Kushagra-0801
Copy link
Contributor

You are committing directly to upstream?
Commit to your local repo then push to your origin then make a pr to upstream/dev

@VikramjeetD
Copy link
Contributor

VikramjeetD commented Feb 12, 2020

Just fyi, package.lock.json is created by the system from package.json. Do NOT alter it manually. Delete package.lock.json and then do an npm install.

I'm assuming that happened as I'm getting a duplicate key warning in there now, which I doubt would happen through npm install.

amrataansh pushed a commit to amrataansh/ChronoFactorem that referenced this pull request Jan 23, 2022
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.

5 participants