Hyunji Jane Lee

In this post, I am going to describe the journey of the release 4.0. Release 4.0 is the 3 weeks project. In the first week, I chose the project to work on. As the issue I chose required knowledge I do not have any idea (Gatsby and Nextjs), I need to learn these. In the second week, I learned the Gatsby and Nextjs to read the document on the Next official website. Also, I checked the pull request other people already created for the project. And this week, I started writing codes to resolve the issue. It was hard to begin to migrate the pages from Gatsby to the Nextjs. I needed to google a lot to find the proper way to migrate the code for the project. The components I was assigned are Error page, SEO, and SearchHelp components. The SEO component is relatively easy because the Next official website indicated how to do it most. However, the Error page is the most difficult part for me. When I googled how to make the Nextjs Errorpage, most people recommend to use the JavaScript extension

For release 4.0, I need to work on a more difficult task than other issues I've worked on. The project I chose is Telescope which is the internal project of this course. The blog post for part 1: why I chose this project is the following:  https://hyunjijanelee.blogspot.com/2020/11/release-40-part-1.html As I have no idea about GatsbyJS and Next.js and don't know how the front-end works on the Telescope project, I've decided to spend my time this week researching and communicating. Firstly, I communicated with the Telescope community. As I heard the task I take (error page) is partly done, I asked the person who took this before what parts are left so I will not mess up another person's work. He replied any of the front-end logic utilizes Gatsby aside from the router. I got I can fully work on this task. Secondly, I read the documents about this task on Telescope GitHub. As many people partly take this issue (one person works on the login page, another person works on t

This is the final lab in the OSD600 course. In this lab, I publish my command-line tool to a package so other users can use my tool! The package I chose is npm because the programming language I used is node.js. This is the detailed instruction of lab 9: https://github.com/Seneca-CDOT/topics-in-open-source-2020/wiki/lab-9 Firstly, I read a  document from npm website  to publish my tool. I ran 'npm init' and created node.js module. I've completed those steps quickly. However, there are two struggles I've got while I'm publishing my tool. One is from the npm account. Before I publish my tool, I should log in npm account. I can check whether I log in or not by entering 'npm whoami'. If I don't have an account, I need to create an account running 'npm adduser'. After verifying the email account, I can login using 'npm login'. The other struggle happened after I log in and tried to publish my tool. It made an error to publish it. I googled why