Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
@getcircuit/ffd
Advanced tools
Stop deploying everything. Detect what functions to deploy with `ffd`.
Stop deploying everything. Detect what functions to deploy with
ffd
.
Under active development. Not ready for usage.
Have you ever needed a tool to automate deployments without pushing all the functions, all the time? ffd
allows you to deploy only functions that changed since your last deploy.
ffd
works by scanning the file where your function is declared. If the file content changes, even if the change is within the dependency tree (via import
or require
) the script spots the difference and generates a new hash for the file.
File hashes are stored in a file called functions-lock.json
created by ffd
:
{
"warning": "DO NOT EDIT. THIS FILE IS AUTO-GENERATED.",
"functions": {
"moduleA": "3bc37d786d96117935bb",
"moduleB": "3d029baae420526b36ca"
}
}
To generate a functions-lock.json
file, ffd
needs a config file. The config file includes information about your functions and their path location.
Sample config file:
{
"myFunctionName1": "./myFunctionName1.js",
"myFunctionName2": "./myFunctionName2.js"
}
Note: In an ideal world, each function you want to deploy would be stored in their own file. If you are not there yet, and ffd
spots a file with more than one function, any changes within that file would trigger an update on every function. That is due to how ffd
works, and the best you can do to avoid this scenario is splitting functions into their own files.
{
// `myFunctionName1` has same path as `myFunctionName3`. Changes within `./myFunctionName1.js` scope
// updates both `myFunctionName1` and `myFunctionName3`. Split functions into files to prevent this.
"myFunctionName1": "./myFunctionName__shared.js",
"myFunctionName2": "./myFunctionName2.js",
"myFunctionName3": "./myFunctionName__shared.js"
}
# works via npm too. volta too.
yarn add firebase-functions-deployer
Package comes with an alias ffd
. Acronym means (f)irebase-(f)unctions-(d)eployer
. As a CLI tool, you should run it via npx
. The CLI expects a --config
parameter to work.
npx ffd --config <path_to_config_file> <options>
Options:
-V, --version output the version number
-c, --config <path_to_config_file> set config file path
-d, --debug <none|errors-only|errors-warnings> output debug info (default: "none")
-h, --help display help for command
MIT
FAQs
Stop deploying everything. Detect what functions to deploy with `ffd`.
The npm package @getcircuit/ffd receives a total of 0 weekly downloads. As such, @getcircuit/ffd popularity was classified as not popular.
We found that @getcircuit/ffd demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 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.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.