New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Configure Typescript for the cli #79

Closed

aelesbao opened this issue Jun 21, 2022 · 0 comments

Milestone

Member

aelesbao commented Jun 21, 2022 •

edited by sync-by-unito bot

Loading

Sample implementation: archway-network/arch3.js#14

┆Issue is synchronized with this Jira Task by Unito

aelesbao mentioned this issue

Replace commander.js with oclif as the CLI framework #78

Closed

aelesbao changed the title ~~Configure Typescript and SWC for the cli~~ Configure Typescript for the cli

aelesbao mentioned this issue

Adjust eslint rules #116

Closed

aelesbao added this to the v2.0.0 - modulor milestone

aelesbao closed this as completed

aelesbao pushed a commit that referenced this issue


          fix(deps): bump node-gyp-build from 4.6.0 to 4.6.1 (#79)

738b70e

Bumps [node-gyp-build](https://github.com/prebuild/node-gyp-build) from
4.6.0 to 4.6.1.
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/prebuild/node-gyp-build/commit/8419abba399ec01f28cfb02b207b659153052a69"><code>8419abb</code></a>
4.6.1</li>
<li><a
href="https://github.com/prebuild/node-gyp-build/commit/94db31ea736429141e963d2bd2a240036a0440dc"><code>94db31e</code></a>
support both bin decls for local node-gyp</li>
<li><a
href="https://github.com/prebuild/node-gyp-build/commit/4479d294ccaed0a7f803a4d6038480fba339e2fa"><code>4479d29</code></a>
Upgrade GitHub Actions (<a
href="https://redirect.github.com/prebuild/node-gyp-build/issues/57">#57</a>)</li>
<li>See full diff in <a
href="https://github.com/prebuild/node-gyp-build/compare/v4.6.0...v4.6.1">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=node-gyp-build&package-manager=npm_and_yarn&previous-version=4.6.0&new-version=4.6.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment