octo VS husky

{ "name": "octo-ssg", "version": "0.1.0", "description": "A tool that allows you to generate static sites based off of text data.", "main": "bin/app.js", "bin": { "octo": "./bin/app.js" }, "scripts": { "prepare": "husky install", "start": "node ./bin/app.js", "build": "npm run prettier && npm run eslint-fix && npm run eslint", "test": "jest", "coverage": "jest --coverage", "eslint": "npx eslint .", "eslint-fix": "eslint --fix .", "prettier": "prettier --write .", "prettier-check": "prettier --check ." }, "repository": { "type": "git", "url": "git+https://github.com/LuigiZaccagnini/octo.git" }, "keywords": [ "ssg", "static", "site", "generator" ], "author": "Luigi Zaccagnini (https://luigizaccagnini.com/)", "license": "GPL-3.0-or-later", "bugs": { "url": "https://github.com/LuigiZaccagnini/octo/issues" }, "homepage": "https://github.com/LuigiZaccagnini/octo#readme", "dependencies": { "boxen": "^4.2.0", "chalk": "2.4", "enzyme": "^3.9.0", "react": "^16.8.6", "react-dom": "^16.8.6", "react-test-renderer": "^17.0.2", "showdown": "^1.9.0", "yargs": "^17.2.1" }, "devDependencies": { "eslint": "^8.1.0", "husky": "^7.0.4", "jest": "^27.3.1", "prettier": "2.4.1" } }

This week, I choose Luigi octo to work on. He has 14 stars for his project so it a bit pressure but I will take it. You can check out my PR-20

Welcome to another post about my project Octo! In this blog I am going to go over:

I have choose this project to add more tests into it. I see Luis does not have tests for textToHTML function yet, so I decide to add it for him, and then I create a pull request with three successful pass in nodes. My testing still needs to be improved a lot because it takes some times to think about it, and I would love to add more tests into my program covering all aspects of it.

Hello! Welcome to another blog post about my open source project Octo. If you're new to my blogs, Octo is an open source static site generation tool created by me! Today I am going to review the process of writing tests and explain how I implemented them in my project.

Welcome to another blog post about the journey of Octo, the open source tool for static site generation! Today I will be going over how I added static analysis tooling into the project and how you can do the same for your open source projects!

Now that I have Markdown finished for Octo I have filed some issues for the next steps of what I would like to be down for the tool. Some of the features I want are:

Hello Everyone! Welcome to my weekly blog post about my journey in Open Source. This week I will be focusing on my experience with refactoring my code for Octo and working with the rebasing feature with Git. I also wanted to share that while writing these blog posts, I will also be posting about Hacktoberfest every week until the end of October so be sure to read those blog posts as well.

First of all, I head into his repo and create another issue telling him what I am going to improve his code. This new feature would allow the ability to use a configuration file within the SSG to allow users specifying the config file instead of typing a long argument. Once he assigns me to the issue, I start to do my work as soon as possible. To be honest, the way he writes his code is completely different from my logic, so it is quite hard for me to understand what is going on inside there. It took me a few hours completing my task. One thing I noticed in his code was that he declared the type for parameter separately, which I should practice how to do this inside my future code. Then I sent him a pull request, we had a conversation to discuss about how we can fix the code and he could merge my code into his branch.

Welcome to my blog post about merging multiple features with my personal project! This time around I will be talking about the two new features I added to the Octo project. The two new features I added are:

Reading Biome doc I also switched from husky to lefthook.

Dive deeper into the world of Husky with the official documentation. Explore the capabilities of Standard Version through its comprehensive documentation. Unravel the mysteries of semantic-release with its detailed documentation. Discover the versatility of bumpp with its comprehensive documentation.

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.

We were already using lint-staged and have a pre-commit hook in place using Husky in our project for linter and prettier. So it made sense to add a check here.

Now, let's talk about Husky. It's a wonderful tool that enables you to run scripts on any Git hooks. We'll add a pre-commit hook to run ESLint and Stylelint checks before committing. This ensures that we don't commit code with errors.

In all my projects I use husky, lint-staged and commitlint.