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.
[UPDATED: 2021-03-30]
We already have @nuxtjs/composition-api. It has useAsync function for the purpose.
Vue.js will introduce new composition API (a.k.a. function API).
It’s really great API but I wonder how to combine with Nuxt.js asyncData w/ this new API.
I find solutions and write about it though Nuxt.js might change its APIs.
Most people might not do this, but some try to use composite primary keys in Rails application.
Yes, I met this situation. And they used composite_primary_keys gem.
I’m writing code with React and TypeScript lately and using React Hooks in the app.
This new APIs makes the React app development very easier and I love it!