DEV Community: Seimei Matsusaki

About Eslint configuration (Airbnb style option for a Typescript project)

Seimei Matsusaki — Sun, 04 Sep 2022 06:12:40 +0000

Since my team recently has decided to introduce Eslint (Typescript + Airbnb style), I was researching how to set up yesterday.

When I read some articles about the configuration, some of the authors directed to choose the Airbnb option during initialization with an image like below:

However, I found that the "Airbnb" option didn't appear when I was initializing the configuration. Only "Standard" and "XO" are available on the latest version (8.23.0):

Curious to say, the "Airbnb" option appeared when I answered "No" to a question, "Does your project use Typescript?":

So, what was wrong? This took me a while to figure out why.

After I did some research on the cause, I realized that the version of my Eslint was the cause. In short, the "Airbnb" and "Google" style options are gone from 8.7.0 for some reason; meanwhile 8.6.0 or before, these were okay:

As you can see, even if I select "Yes" to Typescript, the options are selectable. Nice.

But, I'm still in the middle of the configuration, so there is no guarantee that this is the correct way to go, but I just wanted to share this finding.

Learning Finnish software engineering vocabulary

Seimei Matsusaki — Thu, 21 Apr 2022 00:54:50 +0000

Before I wrote this article, I was wondering if it would be OK to post this to Dev.to. But since this is not a 100% off topic, I decided to post.

Do you study another language besides English?
In my case, Yes.

I have been learning Finnish since 4 years ago. In case you don't know what it is, it is an official language in Finland, and also known as one of the hardest languages for English speakers. You might get a question like, "Hmm, did you live in Finland before?" or "Do you have friends there?" The answer is no. It is a long story why I started learning the language, so I don't write detail here. But in short, I was a big fan of Heavy metal from the country, and that's the beginning.

Anyway, as I was gradually able to read real Finnish (i.e., not Easy-Finnish) articles, I began to want to learn software related vocabulary in Finnish. However, as I expected, I was not able to find a good list to start. I found some lists but there were for more general words. So, I googled or looked up in a dictionary, and jot down one by one. Here is part of my notes:

VOCAB LIST
argument : argumentti
array : taulukko
backend : back end
class : luokka
click (verb): klikata
cache : välimuisti
code : koodi
colon (:) : kaksoispiste
constructor : konstruktori
compile (verb): kääntää
computer : tietokone
cookie : eväste
data : tieto
database : tietokanta
define (verb): määritellä
deploy (verb): sijoittaa
developer : kehittäjä
domain name : verkkotunnus
download (verb) : ladata
engineer : insinööri
file : tiedosto
folder : kansio
frontend : front end
function : funktio
integer : kokonaisluku
keyboard : näppäimistö
operating system : käyttöjärjestelmä
namespace : nimiavaruus
object oriented programming : olio-ohjelmointi
parameter : parametri
performance : suorituskyky
polymorphism : polymorfismi
process : prosessi
programming : ohjelmointi
responsive : responsiivinen
save (verb) : tallentaa
semicolon (;) : puolipiste
server : palvelin
session : istunto
software : ohjelmisto
software developer: ohjelmistokehittäjä
software engineer : ohjelmistoinsinööri
source code: lähdekoodi
terminal : terminaali
test : testi
user interface : käyttöliittymä
value : arvo
variable : muuttuja
webpage : verkkosivu
website : verkkosivusto

I cannot confirm if those words are really used in actual workplaces because I have no Finnish friends. But I hope this list can save someone's time.

Before I close this post, I want to write little about my learning experience of this language so far. Its grammar is surely hard but hardest part for me is listening comprehension. Unlike major languages such as Spanish, there is a very limited number of intermediate level listening stuff with subtitles, so I lost where to start when I was leaving Easy-Finnish materials. This is still a tough issue. Fortunately, I found some Finnish youtuber videos with subtitles, so I continue this journey.

Attempted to deploy Next.js app with Docker to Heroku

Seimei Matsusaki — Sat, 02 Apr 2022 22:04:07 +0000

[Updated on 11/23/2022: Because Heroku is going to remove free dynos, I deleted my app on Heroku]

Last week, I was able to deploy a simple Express server to Heroku with Docker after struggling for an almost entire day. And this time, I wanted to try the same deployment method, Container Registry & Runtime (Docker Deploys) for a Next.js app.

For the sake of simplicity, I used create-next-app command to create a sample Next.js app and used the generated code as is. Here is the source code just in case.

Here are steps I took after I built the app.

1. Add Dockerfile (and .dockerignore)
This is from my Dockerfile:

Nothing special but I needed to do little research on the last line. Since Heroku doesn't allow us to publish a particular port, I had to make my Next.js app listen to the environment variable PORT to which Heroku assigns a random port number.

2. Create a Heroku app on Heroku
I made an app "docker-test-with-nextjs" through Heroku GUI.

3. Log in Heroku on terminal
by the following commands:
heroku login
heroku container:login

4. Add a remote to my local repository
My heroku app name is "docker-test-with-nextjs", so I typed
heroku git:remote -a docker-test-with-nextjs

5. Build, push and release an image
Build an image and push to Heroku:
heroku container:push web

Release the image:
heroku container:release web

6. Wait for seconds and the app is deployed
At last, I could see the app on Heroku👍

Overall, I was able to complete the deployment much quicker than I thought. This was a good experiment and now I can move on deployment of a real Next.js app.

Notes on Express server deployment with Docker to Heroku

Seimei Matsusaki — Sun, 27 Mar 2022 14:10:14 +0000

Phew.. I ended up to spend the whole Saturday trying to deploy a very simple Express server to Heroku. Heroku documentation looked easy at first glance, but I got many errors and needed to do research, but I finally made the server work (src).

Here are my three notes about the deployment.
I hope these can help someone save his/her time in the future.

1. Dockerfile name needs to start with "D", not "d"

OK: "Dockerfile"
WRONG : "dockerfile"

For some reason, a Heroku CLI command heroku container:push doesn't recognize "dockerfile". You will see "No images to push" error then.

2. Use "web" as the process-type
Ref: Container Registry & Runtime (Docker Deploys)

In order to build an image and push to Heroku,
the following command is directed to use.

heroku container:push <process-type>

For a simple web-server case like mine,
"web" was the correct process type.
So, this was the correct command:

heroku container:push web

If you are wondering where "process-type" comes from,
here is an official documentation page:

Dynos and the Dyno Manager

According to it, there are three process types: "Web", "Worker", "One-off".

Since I wasn't sure what the "<process-type>" referred to, I typed an image tag at first. Yes, this was wrong. It was deployed on Heroku; however, it ended up in a "H14" "No web processes running" error.

3. Port # is given through an environment variable PORT
Ref: Setting the port for node.js server on Heroku
I wasn't sure how to publish a port on Heroku.
In short, we cannot freely publish any ports unfortunately.

instead, a port # is given through PORT variable by Heroku,
and it is what the app needed to listen to.

in my case, my app checks PORT variable when it starts,
so i didn't need any modification:

const port = process.env.PORT || 8080;