Merge pull request #14 from MeshJS/feature/refactor-packge

Feature/refactor packge

.github/workflows/npm-publish.yml

@@ -34,8 +34,10 @@ jobs:
             - name: Get package version from main branch before merge
               id: pre-merge-version
               run: |
-                  PRE_MERGE_VERSION=$(node -p "require('./package.json').version")
-                  echo "pre_merge_version=$PRE_MERGE_VERSION" >> "$GITHUB_OUTPUT"
+                  CSL_PRE_MERGE_VERSION=$(node -p "require('./packages/csl/package.json').version")
+                  COMMON_PRE_MERGE_VERSION=$(node -p "require('./packages/common/package.json').version")
+                  echo "csl_pre_merge_version=$CSL_PRE_MERGE_VERSION" >> "$GITHUB_OUTPUT"
+                  echo "common_pre_merge_version=$COMMON_PRE_MERGE_VERSION" >> "$GITHUB_OUTPUT"
 
             - name: Checkout main branch at commit after merge
               uses: actions/checkout@v4
@@ -45,21 +47,43 @@ jobs:
             - name: Get package version from main branch after merge
               id: post-merge-version
               run: |
-                  POST_MERGE_VERSION=$(node -p "require('./package.json').version")
-                  echo "post_merge_version=$POST_MERGE_VERSION" >> "$GITHUB_OUTPUT"
+                  CSL_POST_MERGE_VERSION=$(node -p "require('./packages/csl/package.json').version")
+                  COMMON_POST_MERGE_VERSION=$(node -p "require('./packages/common/package.json').version")
+                  echo "csl_post_merge_version=$CSL_POST_MERGE_VERSION" >> "$GITHUB_OUTPUT"
+                  echo "common_post_merge_version=$COMMON_POST_MERGE_VERSION" >> "$GITHUB_OUTPUT"
 
             - name: Compare versions
               id: compare-versions
               run: |
-                  if [[ "${{ steps.pre-merge-version.outputs.pre_merge_version }}" != "${{ steps.post-merge-version.outputs.post_merge_version }}" ]]; then
-                      echo "version-updated=true" >> "$GITHUB_OUTPUT"
+                  if [[ "${{ steps.pre-merge-version.outputs.csl_pre_merge_version }}" != "${{ steps.post-merge-version.outputs.csl_post_merge_version }}" ]]; then
+                      echo "csl-version-updated=true" >> "$GITHUB_OUTPUT"
                   else
-                      echo "version-updated=false" >> "$GITHUB_OUTPUT"
+                      echo "csl-version-updated=false" >> "$GITHUB_OUTPUT"
                   fi
+                  if [[ "${{ steps.pre-merge-version.outputs.common_pre_merge_version }}" != "${{ steps.post-merge-version.outputs.common_post_merge_version }}" ]]; then
+                      echo "common-version-updated=true" >> "$GITHUB_OUTPUT"
+                  else
+                      echo "common-version-updated=false" >> "$GITHUB_OUTPUT"
+                  fi
+
+    publish-common:
+        needs: [build, check-version]
+        if: needs.check-version.outputs.common-version-updated == 'true'
+        runs-on: ubuntu-latest
+        steps:
+            - uses: actions/checkout@v4
+            - uses: actions/setup-node@v4
+              with:
+                  node-version: 20
+                  registry-url: https://registry.npmjs.org/
+            - run: yarn ci
+            - run: cd packages/common && npm publish --access public
+              env:
+                  NODE_AUTH_TOKEN: ${{secrets.npm_token}}
 
-    publish-npm:
+    publish-csl:
         needs: [build, check-version]
-        if: needs.check-version.outputs.version-updated == 'true'
+        if: needs.check-version.outputs.csl-version-updated == 'true'
         runs-on: ubuntu-latest
         steps:
             - uses: actions/checkout@v4
@@ -68,6 +92,6 @@ jobs:
                   node-version: 20
                   registry-url: https://registry.npmjs.org/
             - run: yarn ci
-            - run: npm publish --access public
+            - run: cd packages/csl && npm publish --access public
               env:
                   NODE_AUTH_TOKEN: ${{secrets.npm_token}}

.gitignore

@@ -1,7 +1,117 @@
-/node_modules
-/.idea
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+*.lcov
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# TypeScript v1 declaration files
+typings/
+
+# TypeScript cache
+*.tsbuildinfo
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Microbundle cache
+.rpt2_cache/
+.rts2_cache_cjs/
+.rts2_cache_es/
+.rts2_cache_umd/
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+.env.*
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+
+# Next.js build output
+.next
+
+# Nuxt.js build / generate output
+.nuxt
+
+# Gatsby files
+.cache/
+# 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
+
+# vuepress build output
+.vuepress/dist
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# TernJS port file
+.tern-port
+
+# production
 dist
 
-# dotenv
-.env*
-!.env.example
+# misc
+.DS_Store
+
+_local
+.rollup.cache
+
+# local testing on new features
+localTest.tsx
+
+tmp

.husky/pre-commit

@@ -1,6 +1,6 @@
 #!/usr/bin/env sh
 . "$(dirname -- "$0")/_/husky.sh"
 
-npx lint-staged
-yarn lint
-yarn test
+yarn
+yarn test
+yarn ci

CODE_OF_CONDUCT.md

@@ -0,0 +1,127 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,5 @@
+# Welcome to Mesh contributing guide
+
+Thank you for investing your time in contributing to this project! Any contribution you make will help you write reusable codes for your application and build up Cardano development space as a whole. :sparkles:. 
+
+Read our [Code of Conduct](./CODE_OF_CONDUCT.md) to keep our community approachable and respectable.