zapier-platform-schema
Advanced tools
Schema definition for CLI apps in the Zapier Developer Platform.
This is the schema for Zapier integrations.
For documentation:
See CONTRIBUTING.md and ARCHITECTURE.md of this package in particular.
Useful commands:
yarn to install packages and get startedyarn lint to lint codeyarn test to run testsyarn smoke-test to run smoke testsyarn coverage to run tests and display test coverageyarn validate to run tests, smoke tests, and linteryarn export to update the exported-schema (even if only the version changes)yarn docs to update docs (even if only the version changes)yarn build to update docs and the exported-schema (even if only the version changes)Only do this after merging your PR to main.
yarn version --[patch|minor|major] will pull, test, update exported-schema, update docs, increment version in package.json, push tags, and publish to npmFAQs
Schema definition for CLI apps in the Zapier Developer Platform.
The npm package zapier-platform-schema receives a total of 21,702 weekly downloads. As such, zapier-platform-schema popularity was classified as popular.
We found that zapier-platform-schema demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 12 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
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.