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

Next 8 dependencies #38

Closed
wants to merge 3 commits into from
Closed

Next 8 dependencies #38

wants to merge 3 commits into from

Conversation

econdie
Copy link
Contributor

@econdie econdie commented Feb 13, 2019

Next v8.0.0 was officially released so this will get rid of the peer dependency warning when using next-seo in a project on the new version. I ran tests with no issues. Also I can suggest only having one of yarn.lock or package-lock.json in root directory. i.e. delete/gitignore the package-lock.json and only support yarn in this project for managing dependencies or vice-versa.

@econdie
Copy link
Contributor Author

econdie commented Feb 13, 2019

looks like it wants the updated package-lock - but running into some errors in e2e when attempting to install dependencies with npm instead of yarn.

@garmeeh
Copy link
Owner

garmeeh commented Feb 13, 2019

I just removed the yarn.lock file on your branch to see if that helps. I probably mistakenly committed that at some stage.

@garmeeh
Copy link
Owner

garmeeh commented Feb 13, 2019

😢 That didn't work either. Just fixed it on master there. That resulted in the conflicts so to save you the hassle of solving those I pushed the changes you had to master and released a patch. So it's available now @1.10.1.

Thanks for the PR either way and sorry about the hassle 😃 I will add yarn.lock to .gitignore to avoid this.

@garmeeh garmeeh closed this Feb 13, 2019
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.

2 participants