Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@storm-software/cloudflare-tools

Package Overview
Dependencies
Maintainers
2
Versions
61
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@storm-software/cloudflare-tools

⚡The Storm-Ops monorepo contains utility applications, tools, and various libraries to create modern and scalable web applications.

  • 0.6.0
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
34
decreased by-56.41%
Maintainers
2
Weekly downloads
 
Created
Source
Storm Software

WebsiteGitHubDiscordDocsContactReport a Bug

This package is part of the ⚡Storm-Ops monorepo. The Storm-Ops packages include CLI utility applications, tools, and various libraries used to create modern, scalable web applications.

💻 Visit stormsoftware.com to stay up to date with this developer


Version  Nx NextJs Commitizen friendly Semantic-Release documented with docusaurus GitHub Workflow Status (with event)

[!IMPORTANT] This repository, and the apps, libraries, and tools contained within, is still in it's initial development phase. As a result, bugs and issues are expected with it's usage. When the main development phase completes, a proper release will be performed, the packages will be availible through NPM (and other distributions), and this message will be removed. However, in the meantime, please feel free to report any issues you may come across.


Storm Cloudflare Tools

A package containing tools for managing a Storm workspace. It includes various Nx generators and executors for common development tasks.

This library was generated with Nx.

Installing

Using pnpm:

pnpm add -D @storm-software/cloudflare-tools
Using npm
npm install -D @storm-software/cloudflare-tools
Using yarn
yarn add -D @storm-software/cloudflare-tools

Executors

The following executors are available in this package to invoke common tasks for the workspace's projects:

Cloudflare Worker Publish

Publish a Cloudflare worker using the Wrangler CLI

Example

This executor can be used by executing the following in a command line utility:

nx run my-project:cloudflare-publish

Please note: The cloudflare-publish executor should be included in the desired projects's project.json file.

Options

The following executor options are available:

OptionTypeDescriptionDefault
namestringName of the Worker.
noBundlebooleanSkip Wrangler’s build steps and directly deploy script without modification. Particularly useful when using custom builds.
envstringPerform on a specific environment.
outdirstringPath to directory where Wrangler will write the bundled Worker files.
compatibilityDatestringA date in the form yyyy-mm-dd, which will be used to determine which version of the Workers runtime is used.
compatibilityFlagsstring[]Flags to use for compatibility checks.
latestbooleanUse the latest version of the Workers runtime.true
assetsstringRoot folder of static assets to be served. Unlike --site, --assets does not require a Worker script to serve your assets.
sitestringRoot folder of static assets for Workers Sites.
siteIncludestring[]Array of .gitignore-style patterns that match file or directory names from the sites directory. Only matched items will be uploaded.
siteExcludestring[]Array of .gitignore-style patterns that match file or directory names from the sites directory. Matched items will not be uploaded.
varstring[]Array of key:value pairs to inject as variables into your code. The value will always be passed as a string to your Worker.
definestring[]Array of key:value pairs to replace global identifiers in your code.
triggersstring[]Cron schedules to attach to the deployed Worker. Refer to Cron Trigger Examples.
routesstring[]Routes where this Worker will be deployed.
tsConfigstringPath to a custom tsconfig.json file.
minifybooleanMinify the bundled script before deploying.
nodeCompatbooleanEnable node.js compatibility.
keepVarsbooleanIt is recommended best practice to treat your Wrangler developer environment as a source of truth for your Worker configuration, and avoid making changes via the Cloudflare dashboard. If you change your environment variables or bindings in the Cloudflare dashboard, Wrangler will override them the next time you deploy. If you want to disable this behavior set keepVars to true.

Cloudflare Worker - Serve executor

Serve a worker locally for development using the Wrangler CLI

Example

This executor can be used by executing the following in a command line utility:

nx run my-project:serve

Please note: The serve executor should be included in the desired projects's project.json file.

Options

The following executor options are available:

OptionTypeDescriptionDefault
namestringName of the Worker.
noBundlebooleanSkip Wrangler’s build steps and show a preview of the script without modification. Particularly useful when using custom builds.
envstringPerform on a specific environment.
compatibilityDatestringA date in the form yyyy-mm-dd, which will be used to determine which version of the Workers runtime is used.
compatibilityFlagsstring[]Flags to use for compatibility checks.
latestbooleanUse the latest version of the Workers runtime.true
ipstringIP address to listen on, defaults to localhost.
portnumberPort to listen on.8787
inspectorPortnumberPort for devtools to connect to.
routesstring[]Routes to upload.
hoststringHost to forward requests to, defaults to the zone of the project.
localProtocol"http" | "https"Protocol to listen to requests on."http"
localUpstreamstringHost to act as origin in local mode, defaults to dev.host or route.
assetsstringRoot folder of static assets to be served. Unlike --site, --assets does not require a Worker script to serve your assets.
sitestringRoot folder of static assets for Workers Sites.
siteIncludestring[]Array of .gitignore-style patterns that match file or directory names from the sites directory. Only matched items will be uploaded.
siteExcludestring[]Array of .gitignore-style patterns that match file or directory names from the sites directory. Matched items will not be uploaded.
upstreamProtocol"http" | "https"Protocol to forward requests to host on."https"
varstring[]Array of key:value pairs to inject as variables into your code. The value will always be passed as a string to your Worker.
definestring[]Array of key:value pairs to replace global identifiers in your code.
tsconfigstringPath to a custom tsconfig.json file.
minifybooleanMinify the script.
nodeCompatbooleanEnable node.js compatibility.
persistTostringSpecify directory to use for local persistence.
remotebooleanDevelop against remote resources and data stored on Cloudflare’s network.
testScheduledbooleanExposes a /__scheduled fetch route which will trigger a scheduled event (cron trigger) for testing during development.
logLevel"debug" | "info" | "log" | "warn" | "error" | "none"Specify Wrangler’s logging level."log"

Generators

The following generators are available with this package to assist in workspace management:

Init Cloudflare tools Nx Plugin for Storm Workspace

Init Cloudflare tools Nx Plugin in the Storm Workspace

Options

The following executor options are available:

OptionTypeDescriptionDefault
unitTestRunner"vitest" | "jest" | "none"Test runner to use for unit tests."vitest"
skipFormatbooleanSkip formatting files.
jsbooleanUse JavaScript instead of TypeScript
template"fetch-handler" | "scheduled-handler" | "hono" | "none"Generate the initial worker using a template.

Please note: Option names followed by * above are required, and must be provided to run the executor.

Create a Cloudflare Worker Application

Create a Cloudflare Worker Application

Options

The following executor options are available:

OptionTypeDescriptionDefault
name *stringThe name of the worker
jsbooleanUse JavaScript instead of TypeScript
projectNameAndRootFormat"as-provided" | "derived"Whether to generate the project name and root directory as provided (as-provided) or generate them composing their values and taking the configured layout into account (derived).
tagsstringAdd tags to the application (used for linting).
frontendProjectstringFrontend project that needs to access this application. This sets up proxy configuration.
unitTestRunner"vitest" | "none"Test runner to use for unit tests."vitest"
template"fetch-handler" | "scheduled-handler" | "hono" | "none"Generate the initial worker using a template."fetch-handler"
portnumberThe port in which the worker will be run on development mode8787
accountIdstringThe Cloudflare account identifier where the worker will be deployed
directorystringThe directory of the new application.
rootProjectbooleanCreate worker application at the root of the workspace
skipFormatbooleanSkip formatting files.

Please note: Option names followed by * above are required, and must be provided to run the executor.

Building

Run nx build cloudflare-tools to build the library.

Running unit tests

Run nx test cloudflare-tools to execute the unit tests via Jest.

Storm Workspaces

Storm workspaces are built using Nx, a set of extensible dev tools for monorepos, which helps you develop like Google, Facebook, and Microsoft. Building on top of Nx, the Open System provides a set of tools and patterns that help you scale your monorepo to many teams while keeping the codebase maintainable.


Roadmap

See the open issues for a list of proposed features (and known issues).


Support

Reach out to the maintainer at one of the following places:


License

This project is licensed under the Apache License 2.0. Feel free to edit and distribute this template as you like.

See LICENSE for more information.


Changelog

This project adheres to Semantic Versioning. Every release, along with the migration instructions, is documented in the CHANGELOG file


Contributing

First off, thanks for taking the time to contribute! Contributions are what makes the open-source community such an amazing place to learn, inspire, and create. Any contributions you make will benefit everybody else and are greatly appreciated.

Please try to create bug reports that are:

  • Reproducible. Include steps to reproduce the problem.
  • Specific. Include as much detail as possible: which version, what environment, etc.
  • Unique. Do not duplicate existing opened issues.
  • Scoped to a Single Bug. One bug per report.

Please adhere to this project's code of conduct.

You can use markdownlint-cli to check for common markdown style inconsistency.


Contributors

Thanks goes to these wonderful people (emoji key):

Patrick Sullivan
Patrick Sullivan

🎨 💻 🔧 📖 ⚠️
Tyler Benning
Tyler Benning

🎨
Stormie
Stormie

🚧
All Contributors Add your contributions

This project follows the all-contributors specification. Contributions of any kind welcome!




Storm Software

Fingerprint: 1BD2 7192 7770 2549 F4C9 F238 E6AD C420 DA5C 4C2D

Storm Software is an open source software development organization and creator of Acidic, StormStack and StormCloud.

Our mission is to make software development more accessible. Our ideal future is one where anyone can create software without years of prior development experience serving as a barrier to entry. We hope to achieve this via LLMs, Generative AI, and intuitive, high-level data modeling/programming languages.

If this sounds interesting, and you would like to help us in creating the next generation of development tools, please reach out on our website!


💻 Visit stormsoftware.com to stay up to date with this developer



Keywords

FAQs

Package last updated on 03 Jun 2024

Did you know?

Socket

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.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc