Refactor: move to yarn workspace

Signed-off-by: imtsuki <me@qjx.app>

.gitignore

@@ -1,3 +1,28 @@
+
+# Created by https://www.toptal.com/developers/gitignore/api/yarn
+# Edit at https://www.toptal.com/developers/gitignore?templates=yarn
+
+### yarn ###
+# https://yarnpkg.com/advanced/qa#which-files-should-be-gitignored
+
+# .yarn/unplugged and .yarn/build-state.yml should likely always be ignored since
+# they typically hold machine-specific build artifacts. Ignoring them might however
+# prevent Zero-Installs from working (to prevent this, set enableScripts to false).
+.yarn/unplugged
+.yarn/build-state.yml
+
+# .yarn/cache and .pnp.* may be safely ignored, but you'll need to run yarn install
+# to regenerate them between each branch switch.
+# Uncomment the following lines if you're not using Zero-Installs:
+# .yarn/cache
+# .pnp.*
+
+# End of https://www.toptal.com/developers/gitignore/api/yarn
+
+# Created by https://www.toptal.com/developers/gitignore/api/node
+# Edit at https://www.toptal.com/developers/gitignore?templates=node
+
+### Node ###
 # Logs
 logs
 *.log
@@ -84,7 +109,7 @@ dist
 
 # Gatsby files
 .cache/
-# Comment in the public line in if your project uses Gatsby and *not* Next.js
+# Comment in the public line in if your project uses Gatsby and not Next.js
 # https://nextjs.org/blog/next-9-1#public-directory-support
 # public
 
@@ -103,5 +128,10 @@ dist
 # TernJS port file
 .tern-port
 
-# Vscode setting file
-.vscode
+# Stores VSCode versions used for testing VSCode extensions
+.vscode-test
+
+# End of https://www.toptal.com/developers/gitignore/api/node
+
+
+.DS_Store

hedgehog-lab/README.md → CONTRIBUTING.md

@@ -1,6 +1,3 @@
-> For historical reasons, we have temporarily switched the package manager to NPM
-
----
 # Contributing Guide
 
 ## Setting up your environment
@@ -48,15 +45,15 @@ All commits will be auto-formatted by commitizen following a fluid interface
 
 ### Commit types(draft)
 
-* **feat**: Commits that result in new features. Backward compatible features will release with the next MINOR whereas breaking changes will be in the next MAJOR. The body of a commit with breaking changes must begin with BREAKING CHANGE, followed by a description of how the API has changed.
-* **fix**: Commits that provide fixes for bugs within hedgehog-lab's codebase.
-* **docs**: Commits that provide updates to the docs.
-* **style**: Commits that do not affect how the code runs, these are simply changes to formatting.
-* **refactor**: Commits that neither fixes a bug nor adds a feature.
-* **perf**: Commits that improve performance.
-* **test**: Commits that add missing or correct existing tests.
-* **chore**: Other commits that don't modify core or test files.
-* **revert**: Commits that revert previous commits.
+- **feat**: Commits that result in new features. Backward compatible features will release with the next MINOR whereas breaking changes will be in the next MAJOR. The body of a commit with breaking changes must begin with BREAKING CHANGE, followed by a description of how the API has changed.
+- **fix**: Commits that provide fixes for bugs within hedgehog-lab's codebase.
+- **docs**: Commits that provide updates to the docs.
+- **style**: Commits that do not affect how the code runs, these are simply changes to formatting.
+- **refactor**: Commits that neither fixes a bug nor adds a feature.
+- **perf**: Commits that improve performance.
+- **test**: Commits that add missing or correct existing tests.
+- **chore**: Other commits that don't modify core or test files.
+- **revert**: Commits that revert previous commits.
 
 ## Submitting Changes / Pull Requests(draft)
 
@@ -66,10 +63,11 @@ Before doing any commits, you will want to pull down the latest and greatest fro
 
 ### Pull Requests For hedgehog-lab(draft)
 
-> Pull requests related to the hedgehog-lab core:  
-* For bug fixes and documentation updates submit pull requests to master.  
-* For new features and enhancements submit pull requests to dev
+> Pull requests related to the hedgehog-lab core:
+
+- For bug fixes and documentation updates submit pull requests to master.
+- For new features and enhancements submit pull requests to dev
 
 ### Pull Requests For Docs
 
-For any pull requests related to hedgehog-lab docs, submit your pull request to the master branch.
+For any pull requests related to hedgehog-lab docs, submit your pull request to the master branch.

README.md

@@ -40,4 +40,4 @@ Read our [contributing guide](/hedgehog-lab/README.md) to learn how to develop t
 
 ## License
 
-This project is licensed under the terms of the [Apache-2.0 License](LICENSE).
+This project is licensed under the terms of the [Apache-2.0 License](LICENSE).