@flourish/live-api
Advanced tools
To get started developing the API:
Clone the Flourish API demo and follow the instructions to set it up.
Link the local version of the API, then start the API demo:
(cd $WHEREVER/flourish/api && npm link) cd $WHEREVER/flourish-api-demo npm link @flourish/live-api npm start
Start Flourish locally, and obtain a local API key if you don't already have one.
Open the running API demo on http://localhost:8888/?local=1 (NB: the local=1 parameter ensures this is run against your local Flourish server). Enter your local API key when requested.
Finally, to see the effects of your changes: edit the API code in this directory, and run npm run build inside flourish/api.
NB: each time you want to see a new change propagate, you'll need to rerun npm run build and restart the API demo.
FAQs
Flourish live API
The npm package @flourish/live-api receives a total of 3,431 weekly downloads. As such, @flourish/live-api popularity was classified as popular.
We found that @flourish/live-api demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 24 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
Rust’s crates.io team is advancing an RFC to add a Security tab that surfaces RustSec vulnerability and unsoundness advisories directly on crate pages.
Security News
/Research
Socket found a Rust typosquat (finch-rust) that loads sha-rust to steal credentials, using impersonation and an unpinned dependency to auto-deliver updates.
Research
/Security Fundamentals
A pair of typosquatted Go packages posing as Google’s UUID library quietly turn helper functions into encrypted exfiltration channels to a paste site, putting developer and CI data at risk.
