🎺 CHANGELOG 🎺 #166
Replies: 16 comments 15 replies
-
Some improvements have been done yesterday on the documentation. Thanks to @smblee. See #160 Also, all v2 presets have been updated to the latest v9.5 version. See #161 Today, dependencies have been upgraded too, following a very strict process to make sure to avoid regressions. See #163 and #165 |
Beta Was this translation helpful? Give feedback.
-
Today, we released a new example with an optional catch-all route. #173 |
Beta Was this translation helpful? Give feedback.
-
Yesterday, we released a new feature related to GitHub Action: #147 Today, we released a few improvements regarding GitHub Action: #180 |
Beta Was this translation helpful? Give feedback.
-
Today, we released a few new features/enhancements:
|
Beta Was this translation helpful? Give feedback.
-
Today, we released a new feature: This will be handy within NRN (I was tired having to manually assign the staging domain every time I deploy to staging) and I also use it to update my own customers "preview" platform automatically, which always has the same url for them that mustn't change. |
Beta Was this translation helpful? Give feedback.
-
Today, we updated the changelog with many changes that have happened those past 2 weeks. We've greatly improved the automation around CI/CD, in particular regarding automated releases, and a new webhook feature for you to be notified when a Vercel deployment is completed.
Those changes mark the end of 2020! 🎉 |
Beta Was this translation helpful? Give feedback.
-
Big documentation update today, added new pages (API Endpoints, Scripts and utilities) that weren't covered at all before today.
Also, the existing documentation has been improved a lot.
|
Beta Was this translation helpful? Give feedback.
-
Today, we've updated most dependencies, including Next.js from
Migration guide:
I guess that's it for the migration guide, I hope it helps. Let us know! |
Beta Was this translation helpful? Give feedback.
-
Today, we release a few changes that affect all pages and highly improve developer experience regarding error handling using Sentry. All Sentry errors will now contain a lot more information about the page (pageProps, router, etc).
Following this update, we recommend changing the following tags in your Sentry > Slack alerts:
See https://unlyed.github.io/next-right-now/guides/monitoring/setup-sentry.html#configuring-sentry-alerts for more documentation |
Beta Was this translation helpful? Give feedback.
-
Today, we release one of our biggest PR: Storybook support. All Next Right Now components have been documented and are available at https://nrn-v2-mst-aptd-at-lcz-sty-storybook.vercel.app/ The whole thing is completely automated using GitHub Actions, and the Storybook static site is hosted on Vercel. Each preset will have its own Storybook. At this time, only the
|
Beta Was this translation helpful? Give feedback.
-
Today, we release one of our most significant change about the folder structure.
|
Beta Was this translation helpful? Give feedback.
-
We released an integration with GitHub Deployments with #280 All Vercel deployments will now be referenced in https://github.com/UnlyEd/next-right-now/deployments. Doc: https://unlyed.github.io/next-right-now/reference/github-environments Also, PR will contain a summary of the latest deployment at the bottom: |
Beta Was this translation helpful? Give feedback.
-
Another small update today, #282 A few path rules have been set for all deployment workflows, so they don't trigger needlessly when unrelated files are changed. Also, the documentation has been updated with a few additions that were built-in for quite a long time but weren't documented: |
Beta Was this translation helpful? Give feedback.
-
We have had a few long-awaited releases today:
Due to webpack 5, we encountered a few issues described in the PR.
|
Beta Was this translation helpful? Give feedback.
-
It's been a while I hadn't kept up with the changes to be announced. Here's what happened since May:
NRN now uses NextJS 11! 🎉The update was super smooth, most of the time spent was related to ESLint, which is now built-in. After testing out the Also, I've worked to increase the Core Web Vitals by looking at accessibility/perf issues and more. The "preload" feature is also a great addition if you need shared static data that should only be fetched once. It's been used for both the DB and the i18n translations. It has decreased the build time. Also, less pages are generated now (only those that should be). We use React "strict mode" by default now, too. Fonts also have been re-worked completely, following Vercel & Lee Robinson best practices! Another huge change is in the way the |
Beta Was this translation helpful? Give feedback.
-
A few changes, that mostly affect the API endpoints:
I learned about some limitations of AWS Lambda, and now understand we need to This came as a surprise, and is an odd behavior that should be documented and explained more. |
Beta Was this translation helpful? Give feedback.
-
🎺 Full CHANGELOG: https://unlyed.github.io/next-right-now/changelog
I'm trying out using Github Discussion to talk about what changes on the repository. I like the idea of showing off what's done to people who're interested to learn about it. Also, I find it more interesting than just a traditional changelog, because it allows discussion/interaction about what has changed.
Feel free to comment below about what you think of that. 😃
Beta Was this translation helpful? Give feedback.
All reactions