You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vscode eslint plugin wasn't picking up next config without specifying directory (020f378)
Breaking Changes
Next 12
See the Next docs to be aware of all changes in version 12.
The one we’ve run into the most is their change from wrapping next/image with a span from a div. We’ve targeted this element in SCSS files before, and needed to manually update.
Redirects
To make our redirects more DRY (and the logic easier to fix bugs with), we have a new lib/checkRedirects.js file. To use, you’ll need to make slight changes to any ..slug.js files (example).
We’ve also added cache expiration when redirects change. You’ll want to add the custom variables to your functions.php, then you can simply drop in an updated webhooks.php
VS Code made changes that require an updated stylelint. We’ve made these changes, but there is one you’ll need to make to your package.json: cd website && yarn add stylelint-config-standard-scss -D && yarn remove styleint-config-standard
Graphql restructure
We’ve moved lib/wordpress.js to lib/wordpress/index.js, and now import customizable queryContent.js and queryGlobals.js files. This allows us to separate bubs-next scaffolding from per project customizations.
To upgrade, you’ll want to clone the structure from a recent version of bubs-next, and copy your specific graphql the content and global files. If you’ve customized more heavily and written additional custom queries, you’ll need to incorporate those as well.
At a minimum, you’ll want to copy over the .husky folder (a part of our automated instructions), and add this line to scripts: "prepare": "cd .. && husky install website/.husky && chmod ug+x website/.husky/* || true".
You can also remove any legacy husky code, e.g. this block:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Features
Bug Fixes
Breaking Changes
Next 12
See the Next docs to be aware of all changes in version 12.
The one we’ve run into the most is their change from wrapping
next/image
with a span from a div. We’ve targeted this element in SCSS files before, and needed to manually update.Redirects
To make our redirects more DRY (and the logic easier to fix bugs with), we have a new
lib/checkRedirects.js
file. To use, you’ll need to make slight changes to any..slug.js
files (example).We’ve also added cache expiration when redirects change. You’ll want to add the custom variables to your functions.php, then you can simply drop in an updated
webhooks.php
Stylelint Upgrade and VS Code
VS Code made changes that require an updated stylelint. We’ve made these changes, but there is one you’ll need to make to your package.json:
cd website && yarn add stylelint-config-standard-scss -D && yarn remove styleint-config-standard
Graphql restructure
We’ve moved
lib/wordpress.js
tolib/wordpress/index.js
, and now import customizablequeryContent.js
andqueryGlobals.js
files. This allows us to separate bubs-next scaffolding from per project customizations.To upgrade, you’ll want to clone the structure from a recent version of bubs-next, and copy your specific graphql the content and global files. If you’ve customized more heavily and written additional custom queries, you’ll need to incorporate those as well.
Husky 7
See the Husky docs for steps on upgrading: https://typicode.github.io/husky/#/?id=migrate-from-v4-to-v7
At a minimum, you’ll want to copy over the .husky folder (a part of our automated instructions), and add this line to scripts:
"prepare": "cd .. && husky install website/.husky && chmod ug+x website/.husky/* || true"
.You can also remove any legacy husky code, e.g. this block:
This discussion was created from the release Q4 2021.
Beta Was this translation helpful? Give feedback.
All reactions