Security News
GitHub Removes Malicious Pull Requests Targeting Open Source Repositories
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
@ambire/common
Advanced tools
This package puts together the core business logic behind Ambire web and mobile apps.
yarn install
After cloning the web or the mobile app and doing npm install
(or yarn install
), delete the node_modules/ambire-common
directory and git clone the ambire-common (this) repository into node_modules/ambire-common
instead.
npm link
(for the web app only)Run yarn install
in ambire-common.
In the ambire-common directory run npm link
In the web app (ambire-wallet) directory, run npm link ambire-common
.
Note: After every npm install
in the web app (ambire-wallet) directory, linking gets lost. You need to perform step 3 again.
Release cycle: every Monday.
When a change is needed, if you need it fast (hot), PR against main
When a change is needed, if you can wait until Monday - PR against develop
If needed, introduce a release branch (example: release/0.16.0
). Merge multiple changes needed for the web or mobile apps QA in there.
When a new version for ambire-common is needed, create a new git tag, issue a new release and describe what has changed. Follow semantic versioning when choosing a tag name.
Always commit in ambire-common code that's compatible with web & mobile both 🤞
Tip during development: When updating the ambire-common version in the web app package.json
, do not manually change your package.json
and run npm install
. Instead, execute npm install "github:AmbireTech/ambire-common#v0.11.0"
. Otherwise, for some reason, package-lock file don't update accordingly and they persist refs to the previous ambire-common version. The issue either comes from npm instelf, or for something really specific in web's package-lock file.
Tip for hotfixes: In case you immediately need the change on PROD, you can simply (temporarily) ref in app's package.json
instead a tag ("ambire-common": "github:AmbireTech/ambire-common#v0.11.2"
) a specific commit SHA ("ambire-common": "github:AmbireTech/ambire-common#2e8639e004044bda3fe7efa3290672d63bfe5f8a"
).
Make sure your code editor has plugins that support the following configuration files: .editorconfig
, .prettierrc
, tsconfig.json
, eslintrc.js
, import-sorter.json
.
FAQs
Common ground for the Ambire apps
The npm package @ambire/common receives a total of 34 weekly downloads. As such, @ambire/common popularity was classified as not popular.
We found that @ambire/common demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.