I’ve been playing with RedwoodJS lately and while it’s still pretty early days for the framework, there is definitely a lot of promise there. I took the time to set up Sentry with RedwoodJS and I figured that it might be good to write these steps down.
If you just want the code, you can go here: https://gist.github.com/rockymeza/7dec7ddb435a6851e6e27d40b1ad0c1a
I was deploying my little RedwoodJS project to Netlify, so this first thing I did was to Google “sentry netlify” and I came up with two useful links:
The Sentry Netlify build plugin deals with submitting releases and source maps to Sentry. The plugin takes care of almost everything, so all I had to do to the code was add the plugin to the
We all know that our render functions are supposed to be pure functions. Purity and immutable data are the basis for performance optimization in React.
That’s great until you need to use time in your app. Time presents some challenges for purity because time is always changing. This can be summed up by the following code snippet:
> new Date() == new Date()
In our system, we have lots of components that rely on the current time in order to render: