@blinkk/editor
Advanced tools
Experimental.
Editor for providing a rich UI for editing structured data with live previews.
See the typescript docs or example.
To start developing on the live editor UI run the following:
yarn install
yarn run serve
Then visit https://localhost:8888/ to iterate and improve the editor.
The live edit server is used to deploy the live editor UI using Cloud Run. It contains logic for connecting to different live edit connectors (such as github and local) and loads in the specialized fields (such as for Grow or Amagaki sites) as needed.
To develop locally run yarn run hosted and visit https://localhost:8080/ and iterate and improve.
If you are developing on the editor UI, use the yarn run serve command from above instead.
The live editor is built for production using a Docker image and Google Cloud Run.
Every commit to main builds the docker image with a :main tag and updates the cloud run image for beta.editor.dev.
Every tag builds the docker image with a version tag (ex: v1.0.5) and the :latest tag then updates the cloud run image for editor.dev.
If there is an issue with the latest release for the prod you can roll back to an earlier version.
To switch the production deployment run make deploy-prod tag=<VERSION> where <VERSION> is the desired version to roll back to.
For example: make deploy-prod tag=v1.0.5.
The builds use gcloud to build and deploy to a Cloud Run service.
The service account needs to be setup to be a member of the -compute@ service account to deploy from cloud build.:
gcloud iam service-accounts add-iam-policy-binding \
--project=$PROJECT \
--member="serviceAccount:$SERVICE_ACCOUNT_EMAIL" \
--role="roles/iam.serviceAccountUser" \
$PROJECT_ID-compute@developer.gserviceaccount.com
The service account also needs to have a set of permissions to be able to build and deploy to cloud run.
FAQs
Structured content editor with live previews.
The npm package @blinkk/editor receives a total of 22 weekly downloads. As such, @blinkk/editor popularity was classified as not popular.
We found that @blinkk/editor 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.
Security News
Security experts warn that recent classification changes obscure the true scope of the NVD backlog as CVE volume hits all-time highs.
Security Fundamentals
Attackers use obfuscation to hide malware in open source packages. Learn how to spot these techniques across npm, PyPI, Maven, and more.
Security News
Join Socket for exclusive networking events, rooftop gatherings, and one-on-one meetings during BSidesSF and RSA 2025 in San Francisco.