This is just my personal feeling. Don’t take it seriously.
Next.js + useSWR
is awesome and gives you a great experience for frontend dev.
But they also sometimes cause trouble, and I explain one of them in this post.
I often forget Node.js stream API and usage.
As the post says, it is for:
This API helps when you do batch operation like processing 100,000 records of a table of PostgreSQL, for example.
I’ve worked with several kinds of web desingers so far. Some are good, others are not.
Lately I experienced bad communication with a web designer. Then I’ve decided to write “what nature a good web designer has” (from my experience) in order to organize my thoughts and avoid such an issue in the future.
I’d used Sass (.scss
) in a Nuxt.js project.
But Nuxt.js doesn’t support Sass natively. Removing node-sass
and sass-loader
will make me easier to maintain the project.
In addition, I have lately heard that PostCSS is modern CSS pre-/post-processor and you should use it. Nuxt.js also supports it w/o installing additional npm packages.
Then I switched from Sass to PostCSS.
One of my participating projects uses Gulp for bundling front-end JavaScript and CSS in a part even in 2020.
It uses browserify internally, but the gulpfile
is really messy and I will try to migrate it to webpack build which I’ve been avoided.
And I’ve found the key points to use Webpack and leave a note.
There are some docker image types, like *-slim
, *-alpine
, etc.
I’ve taken *-alpine
in most cases without thinking deeply, but I found there could have downside of using them yesterday and I googled about this topic.