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

Extension browser changelog doesn't show up in the site #825

Closed
molant opened this issue Sep 13, 2019 · 0 comments · Fixed by #831
Closed

Extension browser changelog doesn't show up in the site #825

molant opened this issue Sep 13, 2019 · 0 comments · Fixed by #831
Assignees
Labels
Milestone

Comments

@molant
Copy link
Member

molant commented Sep 13, 2019

https://webhint.io/about/changelog/ for September 12th there should be a changelog of the extension-browser.

@molant molant added this to the 1909-2 milestone Sep 13, 2019
@molant molant self-assigned this Sep 16, 2019
molant added a commit to molant/webhint.io that referenced this issue Sep 17, 2019
The project had different versions of the same package because of how
hoisting works, `hint`'s `optionalDependencies` (the configurations are
not the latest ones) and how npm handles duplicates and `package-lock.json`.
By removing `package-lock.json` npm will always go fetch the latest
version of the packages and avoid these issues. Also all packages will
be installed in `node_modules` and not inside another folder under it.

Because multiple versions of the same package, the changelog was not
always accurate.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Fix webhintio#825
@molant molant mentioned this issue Sep 17, 2019
2 tasks
molant added a commit to molant/webhint.io that referenced this issue Sep 18, 2019
The project had different versions of the same package because of how
hoisting works, `hint`'s `optionalDependencies` (the configurations are
not the latest ones) and how npm handles duplicates and `package-lock.json`.
By removing `package-lock.json` npm will always go fetch the latest
version of the packages and avoid these issues. Also all packages will
be installed in `node_modules` and not inside another folder under it.

Because multiple versions of the same package, the changelog was not
always accurate.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Fix webhintio#825
molant added a commit to molant/webhint.io that referenced this issue Sep 18, 2019
The project had different versions of the same package because of how
hoisting works, `hint`'s `optionalDependencies` (the configurations are
not the latest ones) and how npm handles duplicates and `package-lock.json`.
By removing `package-lock.json` npm will always go fetch the latest
version of the packages and avoid these issues. Also all packages will
be installed in `node_modules` and not inside another folder under it.

Because multiple versions of the same package, the changelog was not
always accurate.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Fix webhintio#825
molant added a commit that referenced this issue Sep 18, 2019
The project had different versions of the same package because of how
hoisting works, `hint`'s `optionalDependencies` (the configurations are
not the latest ones) and how npm handles duplicates and `package-lock.json`.
By removing `package-lock.json` npm will always go fetch the latest
version of the packages and avoid these issues. Also all packages will
be installed in `node_modules` and not inside another folder under it.

Because multiple versions of the same package, the changelog was not
always accurate.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Fix #825
Close #831
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant