Skip to content
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.

Releases: cloudflare/wrangler-legacy

v1.4.0-rc.0

20 Sep 18:39
Compare
Choose a tag to compare
v1.4.0-rc.0 Pre-release
Pre-release

Changes:

  • edae328 1.4.0-rc.0
  • b7ff500 Merge pull request #509 from cloudflare/feat-kv-additions
  • d6f0140 Merge pull request #639 from cloudflare/alewis/merge-conflicts
  • ed05a78 Merge remote-tracking branch 'origin/master' into feat-kv-additions
  • 178749a Merge pull request #638 from cloudflare/alewis/default-site-bucket
  • f5a3b86 Better file support for kv:put (#633)
  • 90f321e feat #637: add default bucket to generate function
  • e8bb966 Merge pull request #635 from cloudflare/gabbi/fix-asset-manifest-logic
  • cb8a6a8 Remove clone of b64_value
  • 5b7603b Ensure that deletion phase of sync also uses keys with value hashes appended
See More
  • 4768e68 Merge branch 'master' into feat-kv-additions
  • 0705c87 and i oop (fix bad call to format_err)
  • 87d35db catch oversized files
  • 12ecc38 Asset Manifest (#629)
  • 5385c86 Merge pull request #632 from cloudflare/alewis/build-site
  • 359b2e8 code review p3
  • 2e489d9 code review p2
  • 5189f8e code review
  • 798dfc7 cargo clippy
  • 7d4a673 Just like all of it
  • 2c8ef24 Add --site flag to wrangler generate
  • 6518c1d refactor: pass config_path as argument to Manifest::generate
  • 88ccb0f :nailcare: kv:key indentation in main.rs
  • c5d42ad refactor: reorder manifest methods: pub, constructor first
  • b9c3a50 set up verbose logging option for (#626)
  • d8637f6 Merge pull request #616 from cloudflare/alewis/root-toml
  • a52dc3c Ensure that sync uploads new files before deleting removed ones on remote
  • 6cbfb39 Allow user to configure build directory as site.entry-point
  • 595bb89 Use workers-site as build_dir if site is present
  • e8ab108 refactor: define build directory as method on Target
  • fb9a296 Implement large bucket uploads split across multiple bulk KV API requests (#601)
  • 526e45f Merge pull request #615 from cloudflare/alewis/sites-interface
  • 2a674f1 Implement crude version of kv:bucket sync that does not use hashes to determine changed files yet (#614)
  • 8b4d4ad Automagically provision namespace for sites on publish
  • 4634d12 Merge pull request #598 from cloudflare/alewis/negate [ #450 ]
  • d7f3706 Merge pull request #617 from adaptive/master
  • cd28f7b typo correction on CHANGELOG
  • 054ee16 Add logic for getting/creating Site namespace
  • 9996ad6 Code Review: kebab-case flags, no double negatives
  • c049f7e feat #450: support negate flags for publish
  • 286f3cb Merge branch 'master' into feat-kv-additions
  • 6ed6f3f Fix nasty merge issues
  • 82b6727 Refactor kv::print_error to kv::format_error and hoist error printing out of private kv functions (#613)
  • 01e3330 Merge branch 'master' into feat-kv-additions
  • 738bd66 Merge pull request #612 from cloudflare/avery/fix-broken-link
  • d1b7b44 Fix broken kv docs link in changelog
  • 90c54ee Merge pull request #606 from cloudflare/1.3.1
  • 77a8ded Merge pull request #592 from cloudflare/avery/bucket-more-like-big-cup-am-i-right-high-five-very-nice
  • 0c4a46b Use MY_KV instead of KV in examples
  • 9b81b2a Add namespace and binding arguments to bucket
  • 6ac6604 Merge branch 'master' into feat-kv-additions
  • 3e9cee9 Merge remote-tracking branch 'origin/master' into feat-kv-additions
  • c0d408f Merge pull request #530 from cloudflare/alewis/refactor-publish-sites
  • c666c42 feedback: tidy bulk delete path error message
  • d744881 cargo clippy; handle file values to kv:key put in main
  • 61419ab refactor: add kv bucket dir, replace POC code with bucket commands
  • e39b993 Merge branch 'feat-kv-commands' into feat-kv-additions
  • 1cff8f3 Merge branch 'feat-kv-commands' into feat-kv-additions
  • 22a9ce0 Merge pull request #514 from cloudflare/alewis/add-bucket-operations
  • 63415ea separate parse_directory for upload/delete
  • 7c72229 add bucket commands to docs
  • 4d2190a remove use of ref keyword
  • a144833 use failure::bail directly
  • 8f79074 Apply suggestions from code review
  • 0ed02e8 Add bucket::upload, bucket::delete
  • 810f5ab Remove unneeded assets test toml
  • 3652c16 Redesign assets as optional part of kv namespace
  • f47b0d5 Proof of concept: bulk write assets on publish
  • be8571f feat#447: Add 'assets' key to Project

This list of changes was auto generated.

πŸ› 1.3.1

17 Sep 17:52
Compare
Choose a tag to compare
  • Features

    • Environments - EverlastingBugstopper, issue/385

      Wrangler 1.3.0 includes supports for environments, allowing developers to deploy Workers projects to multiple places. For instance, an application can be deployed to a production URL and a staging URL, without having to juggle multiple configuration files.

      To use environments, you can now pass in [env.$env_name] properties in your wrangler.toml. Here's an example:

      type = "webpack"
      name = "my-worker-dev"
      account_id = "12345678901234567890"
      zone_id = "09876543210987654321"
      workers_dot_dev = false
      [env.staging]
      name = "my-worker-staging"
      route = "staging.example.com/*"
      [env.production]
      name = "my-worker"
      route = "example.com/*"

      With multiple environments defined, wrangler build, wrangler preview, and wrangler publish now accept a --env flag to indicate what environment you'd like to use, for instance, wrangler publish --env production.

      To support developers transitioning to environments, we've written documentation for the feature, including further information about deprecations and advanced usage. Check out the documentation here!

    • KV commands - ashleymichal, gabbifish, issue/339

      Wrangler 1.3.0 includes commands for managing and updating Workers KV namespaces, keys, and values directly from the CLI.

      • wrangler kv:namespace

        wrangler kv:namespace allows developers to create, list, and delete KV namespaces, from the CLI. This allows Wrangler users to configure new namespaces without having to navigate into the Cloudflare Web UI to manage namespaces. Once a namespace has been created, Wrangler will even give you the exact configuration to copy into your wrangler.toml to begin using your new namespace in your project. Neat!

        $ wrangler kv:namespace create "MY_KV"
        πŸŒ€  Creating namespace with title "worker-MY_KV"
        ✨  Success: WorkersKvNamespace {
          id: "e29b263ab50e42ce9b637fa8370175e8",
          title: "worker-MY_KV",
        }
        ✨  Add the following to your wrangler.toml:
        kv-namespaces = [
          { binding = "MY_KV", id = "e29b263ab50e42ce9b637fa8370175e8" }
        ]
      • wrangler kv:key

        wrangler kv:key gives CLI users access to reading, listing, and updating KV keys inside of a namespace. For instance, given a namespace with the binding KV, you can directly set keys and values from the CLI, including passing expiration data, such as below:

        $ wrangler kv:key put --binding=KV "key" "value" --ttl=10000
        ✨  Success
      • wrangler kv:bulk

        wrangler kv:bulk can be used to quickly upload or remove a large number of values from Workers KV, by accepting a JSON file containing KV data. Let's define a JSON file, data.json:

        [
          {
            "key": "test_key",
            "value": "test_value",
            "expiration_ttl": 3600
          },
          {
            "key": "test_key2",
            "value": "test_value2",
            "expiration_ttl": 3600
          }
        ]

        By calling wrangler kv:bulk put --binding=KV data.json, I can quickly create two new keys in Workers KV - test_key and test_key2, with the corresponding values test_value and test_value2:

        $ wrangler kv:bulk put --binding=KV data.json
        ✨  Success

      The KV subcommands in Wrangler 1.3.0 make it super easy to comfortably query and manage your Workers KV data without ever having to leave the command-line. For more information on the available commands and their usage, see the documentation. 🀯

    • Reduce output from publish command - EverlastingBugstopper, issue/523

      This PR improves the messaging of wrangler publish.

      Before:

      ✨  Built successfully, built project size is 517 bytes.
      ✨  Successfully published your script.
      ✨  Success! Your worker was successfully published. You can view it at example.com/*

      After:

      $ wrangler publish
      ✨  Built successfully, built project size is 523 bytes.
      ✨  Successfully published your script to example.com/*
    • feat #323: Allow fn & promise from webpack config - [third774], [issue/323][pull/325]

      This PR fixes Wrangler's handling of webpack.config.js files to support functions and promises, as per the Webpack documentation.
      [xtuc]: https://github.com/xtuc
      [issue/477]: #477
      [pull/490]: #490

  • Fixes

    • Have live reload preview watch over entire rust worker directory - gabbifish, pull/535

      This change updates the live reload functionality to watch over the entire Rust worker directory, and does not look for package.json files that do not typically exist for Rust and WASM projects.

    • Fix javascript live preview for linux - gabbifish, issue/517

      This PR fixes an issue with Wrangler's live preview (wrangler preview --watch) functionality on Linux. In addition, it simplifies the console output for a live preview instance, which could get pretty noisy during development!

    • Different emojis for different commands - EverlastingBugstopper, pull/605

      KV subcommands would return the same emoji value in --help output. This PR updates the command-line output to use different emoji, making the output easier to read!

  • Maintenance

    • Add keywords for npm SEO - EverlastingBugstopper, pull/583

      This PR improves the discoverability for wrangler on npm by adding keywords to the installer's package.json.

    • Clean up emoji - xortive, pull/455

      This PR removes some extraneous unicode that keeps our emoji from displaying correctly in certain terminal emulators, especially for multi-codepoint emoji.

  • Documentation

    • Add documentation for init to the README - EverlastingBugstopper, pull/585

      This PR adds documentation in our README for wrangler init, which allows you to begin using an existing project with Wrangler.

    • Remove link to docs for installation because they link back to wrangler README - EverlastingBugstopper, pull/494

    • Minor formatting fix in README.md - kentonv, pull/515

      This PR fixes a small syntax issue in the Wrangler README, causing Markdown lists to render incorrectly.

    • Fix link to Cloudflare Workers preview service - dentarg, pull/472

      This PR fixes a link to the Cloudflare Workers preview service in the Wrangler README.

πŸ’†πŸ»β€β™‚οΈ 1.2.0

16 Aug 22:34
Compare
Choose a tag to compare
  • Features

    • Implement live previewing for wrangler - xortive, pull/451

      The wrangler preview command now supports live previewing! As you develop your project, you can start up a link between your local codebase and the preview service by running wrangler preview --watch. Any updates to your project will be passed to the preview service, allowing you to instantly see any changes to your project. This is a massive improvement to the development process for building applications with Workers, and we're super excited to ship it!

      A huge shout-out to @xortive, who almost single-handedly built this feature during his summer internship at Cloudflare, over the last few months. Amazing work! 😍

    • Authenticate calls to preview service when possible - ashleymichal, issue/423 issue/431 pull/429

      This PR allows developers to use the preview service with account and user-specific functionality, such as KV support inside of the preview service. Previously, attempting to preview a Workers project with KV bindings would cause an error - this PR fixes that, by allowing wrangler preview to make authenticated calls to the preview service.

  • Documentation

  • Fixes

    • Fix ignoring exit code from spawnSync - run-wrangler.js - defjosiah, issue/433 issue/335 pull/432

      This PR fixes an issue where an NPM-installed wrangler would always return an exit code of 0, even when wrangler had errored. This improves wrangler's ability to be scripted, e.g. in CI projects.

  • Maintenance

    • [chore] Deny clippy warnings in CI, run rustfmt in --check mode - xortive, issue/426 pull/435

      This PR updates some of the CI steps for testing Wrangler, to make sure that rust-clippy warnings cause CI to fail. This helps Wrangler code stay well-written and consistent - hooray!

    • Nits: fix clippy warnings - xortive, pull/427

    • Add repository link to Cargo.toml - 56quarters, pull/425

πŸ„β€β™€οΈ 1.1.1

09 Aug 21:03
Compare
Choose a tag to compare
  • Features

    • Install current version, not latest - ashleygwilliams, issue/418

      Previously the NPM installer for wrangler would always pull the most recent release from Github releases, and the installer did not increase version numbers when Wrangler did. Many users found this confusing. Now the installer will increment versions along with Wrangler releases, and point at specific versions rather than the most recent one at the time of installation.

    • Improve JSON errors debuggability - xtuc, pull/394

      This PR improves JSON error output in wrangler. Specifically:

      • If a package.json file fails to decode, wrangler now emits a clearer error:

        $ wrangler build
        ⬇️  Installing wranglerjs...
        ⬇️  Installing wasm-pack...
        thread 'main' panicked at 'could not parse "./package.json": Error("expected `,` or `}`", line: 4, column: 3)', src/libcore/result.rs:999:5
        
      • If the wranglerjs backend returns invalid JSON, it now preserves the output file for further investigation. Note that the console doesn't print the output file location by default, and you will need to pass RUST_LOG=info while running wrangler build, and search for the --output-file=FILE argument passed to wranglerjs:

        $ RUST_LOG=info wrangler build
        ⬇️ Installing wasm-pack...
        [2019-08-09T19:28:48Z INFO  wrangler::commands::build::wranglerjs] Running "/Users/kristian/.nvm/versions/node/v12.1.0/bin/node" "/Users/kristian/src/workers/wrangler/wranglerjs" "--output-file=/var/folders/5x/yzqyqst11n518yl8xl7yv1f80000gp/T/.wranglerjs_output5eREv" # ...
        
      • If the preview service returns invalid JSON, it now emits a clearer error, and the full output can be seen by using RUST_LOG=info.

        Previously:

        $ wrangler preview
        ⬇️ Installing wasm-pack...
        ⬇️ Installing wranglerjs...
        ✨   Built successfully.
        Error: Error("expected value", line: 2, column: 1)
        

        Now:

        $ wrangler preview
        ⬇️ Installing wranglerjs...
        ⬇️ Installing wasm-pack...
        ✨   Built successfully, built project size is 1 MiB. ⚠️  Your built project has grown past the 1MiB size limit and may fail to deploy. ⚠️  ✨
        Error: https://cloudflareworkers.com/script: Server Error: 502 Bad Gateway
        
  • Fixes

    • Fix wrangler config for systems with non-unix EOL - xortive, issue/389

      wrangler config was not properly truncating whitespace from the end of user input, resulting in a panic when trying to use wrangler publish, because wrangler would try to create an HTTP header with invalid characters. Now, wrangler will properly truncate extra whitespace (including \r) from the end of the input into wrangler config.

  • Maintenance

    • Migrate straggler emojis to terminal::emoji - EverlastingBugstopper, pull/382

      This PR updates the last remaining instances where wrangler was using hard-coded emojis for messages, rather than using terminal::emoji. In addition, there are two instances where this PR changes the usage of the β›” emoji to ⚠️.

    • Move test fixtures to their own directory - EverlastingBugstopper, pull/383

      This PR aggregates fixtures used in integration tests into a fixtures directory to
      make it easier to find/use them.

    • Update issue templates to fit Github's data model - EverlastingBugstopper, pull/387

      Our previous issue templates were not picked up by Github's user interface. This PR updates the templates to fit the accepted data model, and adds some style tweaks to make the templates easier to use.

    • Move Emoji formatting/messaging into new functions - ashleymichal, pull/391

      This PR makes improvements to the internal messaging logic of Wrangler, allowing us to be more flexible in how we display information to users.

  • Documentation

    • Update README to include config, env var changes - ashleymichal, pull/379

      In 1.1.0 we changed the config command to be interactive. This PR updates the README to reflect that change.

    • Add section to readme about Vendored OpenSSL - xortive, pull/407

      Wrangler has some external OpenSSL dependencies when installing on Linux -- this PR documents those dependencies, and how to install Wrangler using a vendored OpenSSL feature flag:

      cargo install wrangler --features vendored-openssl
      

πŸ”‘ 1.1.0

30 Jul 23:25
Compare
Choose a tag to compare

Wrangler 1.1.0 includes a number of improvements to documentation and project stability, including:

  • Security

    • Change global config perm - xtuc, pull/286

      This PR improves the security of Wrangler's global config file, by restricting access to Wrangler's global user configuration file (~/.wrangler/config/default.toml) to the user who ran the wrangler config command. For existing Wrangler users, please run wrangler config again on your machine! This will fix the permissions of your global config file to be scoped to your user account.

    • Use stdin instead of arguments for wrangler config - xtuc, pull/329

      We've made the wrangler config command interactive – the previous version of the command, wrangler config $email $apiKey, would be captured by your terminal's history, often exposing that information in a ~/.bash_history or a similar file. The new version of wrangler config will prompt you for your email and api_key via stdin.

      In addition, this PR also adds support for a WRANGLER_HOME environment variable, which will be the location for Wrangler's "home" directory, if you need to customize where Wrangler saves its configuration information.

  • Features

    • Support KV Namespace Configuration - ashleymichal, pull/334, add check + error message for pre 1.1.0 kv namespace format - xortive, pull/369

      Wrangler now supports using Workers KV namespaces in your project! To start using KV with your projects, create a namespace in the Cloduflare Dashboard, and the namespace information to your wrangler.toml configuration file. The kv-namespaces key requires setting a binding (the representation of your namespace in your code) and id, the namespace ID:

      # wrangler.toml
      
      [[kv-namespaces]]
      binding = "TODOS"
      id = "0f2ac74b498b48028cb68387c421e279"

      If you were previously using the undocumented kv-namespaces support in your project config, you'll need to make a few changes to your project to use Wrangler 1.1.0! KV namespaces now need to be created manually, in the Cloudflare Dashboard, to be able to use them in your Wrangler configuration - previous versions of Wrangler created the namespace for you, but the process is now manual, to allow developers to be more explicit about how their KV namespaces are created.

      For users of the previously undocumented kv-namespaces functionality in Wrangler, we've provided a warning and upgrade path, to help you upgrade your KV configuration in your project to the correct format:

      ⚠️  As of 1.1.0 the kv-namespaces format has been stabilized ⚠️
      πŸ’β€  Please add a section like this in your `wrangler.toml` for each KV Namespace you wish to bind: πŸ’β€
      
      [[kv-namespaces]]
      binding = "BINDING_NAME"
      id = "0f2ac74b498b48028cb68387c421e279"
      
      # binding is the variable name you wish to bind the namespace to in your script.
      # id is the namespace_id assigned to your kv namespace upon creation. e.g. (per namespace)
      
      Error: ⚠️  Your project config has an error ⚠️
      

      This is the initial part of a lot of incredible work being done on supporting Workers KV in Wrangler. If you're interested in what's up next, check out our next milestone.

    • Configure Workers KV in your wrangler.toml - ashleymichal, pull/333

      If you've tried to use Workers KV in Wrangler, you've probably had a bad time! This PR, along with #334, build support for handling and correctly uploading KV namespace information with your Wrangler project:

      [[kv-namespaces]]
      binding = "NAMESPACE"
      id = "0f2ac74b498b48028cb68387c421e279"
      
    • Use ENV variables to configure Wrangler - AaronO, pull/225

      Previously, Wrangler required a global configuration file to be able to run. As many users may use Wrangler in situations where they don't have an interactive terminal, meaning they can't instantiate a config file using wrangler config, this PR allows Wrangler to run even if the config file doesn't exist. This change means that users can also configure Wrangler exclusively with environment variables, using $CF_API_KEY for your Cloudflare API key, and $CF_EMAIL for your Cloudflare account email.

    • Adds more descriptive subdomain errors - EverlastingBugstopper, issue/207

      It's super easy to grab a workers.dev subdomain using the subdomain command in wrangler – so easy, in fact, that many people were trying to use it without even having a Cloudflare account! wrangler now warns users when they attempt to add a subdomain without configuring their account_id in wrangler.toml, as well as when you've already registered a subdomain, or if the subdomain you're trying to register has already been claimed.

    • Allow custom webpack configuration in wrangler.toml - EverlastingBugstopper, issue/246

      If you'd like to bring your own Webpack config to your Workers project, you can now specify a webpack_config key in wrangler.toml:

      webpack_config: webpack.prod.js
    • Add issue templates for bug reports and feature requests - gabbifish, issue/250

      To make it easier for us to diagnose problems and support user feedback, we've added issue templates to make it easier for users to submit bug reports and feature requests.

    • Display commands in their defined order - Electroid, [pull/236]

      We've re-arranged the order of the commands when you run wrangler without any subcommands, so that commonly-used commands are easier to find!

    • Show project size on build - xtuc, pull/205

      Once the build is finished, wrangler now prints the compressed size of the script, and, if available, the Wasm binary size:

      $ wrangler publish
      ⬇️ Installing wranglerjs...
      ⬇️ Installing wasm-pack...
      ✨   Built successfully, built project size is 517 bytes. ✨
      
    • Add HTTP prefix to publish command output. - elithrar, pull/198

      Prefix "https://" in front of the "script available" output to allow shells to automatically detect it as a link. Many shells will allow you to click directly on the URL from inside the terminal (such as iTerm's "CMD-Click"), making it much easier to navigate to your subdomains, or any published Workers applications.

    • Build: add message and emoji - xtuc, pull/193

      The wrangler team really loves emoji, so we made sure to send a little bit of ✨ cheer ✨ your way, via a new message and emoji, whenever you use the build subcommand. πŸ’Œ

  • πŸ€• Fixes

    • Remove OpenSSL installation step from README - xortive, issue/355

      Due to an OpenSSL dependency in cargo-generate, Wrangler required developers to install OpenSSL as part of the setup process for using Wrangler. Version 0.3.1 of cargo-generate has removed this requirement, and you no longer need to install OpenSSL manually to use Wrangler. Hooray!

    • Fix issue previewing a project with KV namespaces - ashleymichal, pull/353

      This PR fixes a critical bug where using wrangler preview on a project with Workers KV namespaces causes the command to throw an error.

    • Enforce one Webpack entry in configuration - xtuc, [pull/245]

      wrangler now returns an error during the build process if you use a webpack configuration with more than one export – wrangler needs to have a single known export from webpack to know what to build!

      [pull...

Read more

v1.0.0

01 Jun 19:05
Compare
Choose a tag to compare

Changes:

  • a8fceff 1.0.0
  • ff67536 Merge pull request #191 from cloudflare/fix-npm-install-flock
  • efd91f4 Merge pull request #192 from cloudflare/check-for-keys
  • de67816 fix: remove flock if it exists
  • 2d0ca35 Merge pull request #193 from cloudflare/feat-add-build-emoji
  • 28d1e98 fix(config): better errors for missing config vals
  • 0ab809b Update src/commands/build.rs
  • c5468b1 fix
  • 0438964 feat(build): add message and emoji
  • a02628b fix: make sure to remove lock
See more
  • fa1fe75 Merge pull request #188 from cloudflare/chore-upgrade-binary-install1
  • b87ea75 chore: add lock
  • a76cc6e chore: upgrade deps
  • af8bb57 Merge pull request #185 from cloudflare/fix-npm-install
  • d4d3d70 feat: add flock
  • 0a8eb21 fix(npm): various fixes
  • 0512d85 Merge pull request #161 from cloudflare/docs
  • 81a6ceb Merge pull request #184 from cloudflare/clippy-lints
  • 0251251 fix: address comments
  • a5935ad feat(docs): docs up to date with master
  • 01890d9 fix(style): clippy lints
  • 9e3d74f Merge pull request #181 from cloudflare/ci-logging
  • 52f0b6b fix: syntax
  • 3a320df ci: change logging
  • 311fd90 chore: force ci
  • aaa6d45 Merge pull request #165 from cloudflare/fix-windows-invoke
  • 35610c5 Merge branch 'master' into fix-windows-invoke
  • 7fc96cf Merge pull request #174 from cloudflare/refactor-wranglerjs-installation-2
  • b1e492b Revert "Revert "ci: enable info logging""
  • 4f3f4da Revert "ci: enable info logging"
  • 4519dc2 Merge pull request #173 from cloudflare/refactor-wranglerjs-installation-1
  • 8760001 feat: use latests binary-install
  • 2ecb7ed Merge pull request #160 from steveklabnik/gh117
  • 3930c61 Merge pull request #178 from cloudflare/feat-npm-install
  • b7871c1 feat: add npm install
  • 77d2816 ci: enable info logging
  • 2c52158 fix: fmt
  • f2dc164 Merge branch 'refactor-wranglerjs-installation-1' into refactor-wranglerjs-installation-2
  • c09a731 Merge branch 'master' into refactor-wranglerjs-installation-1
  • 1c8a6a5 Merge pull request #176 from cloudflare/feat-webpack-tests
  • 7556044 feat: add more Webpack tests
  • 7f212fb Merge pull request #175 from cloudflare/feat-enable-wranglerjs-tests
  • 406070a feat: enable wranglerjs tests
  • d1e6c5d Merge pull request #169 from cloudflare/feat-webpack-error
  • 1f35714 fix: install wrangler
  • 3457135 chore(wranglerjs): new version
  • 0a3cfbd Merge branch 'master' into feat-webpack-error
  • e4e299d Revert "refactor: remove controversial part"
  • 159bc50 refactor: remove controversial part
  • e2120e3 Merge branch 'master' into refactor-wranglerjs-installation
  • 71b81eb Merge pull request #172 from cloudflare/refactor-rename-wranglerjs
  • dbd6aef chore(wranglerj): version
  • 0c9458e refactor: rename wranglerjs
  • 2245933 fix: remove ununeed clone
  • 57e8577 Update tests/build.rs
  • c3ee3db fix: unneeded clone
  • f066b22 Merge pull request #162 from cloudflare/init-plz
  • a34de54 feat(command): init
  • 2844ca5 feat: show Webpack error
  • eae0cd1 [skip ci] Revert "ci: enable backstrace logs"
  • 19aea9d fix: remove duplicated create_dir
  • 7b4aa36 Merge pull request #168 from cloudflare/feat-remove-webpack-output2
  • 703e062 feat: remove Webpack output
  • bf6fb75 Update src/commands/publish/mod.rs
  • 8920332 fix: workaround windows rm_dir_all
  • ce7e617 Update src/wranglerjs/mod.rs
  • 36bf188 ci: enable backstrace logs
  • 44a3a66 fix(wranglerjs): remove executable
  • f7d63bb fix: remove npm bin
  • a9de95c fix: import {build_npm_command}
  • 8a48958 fix: Windows commands
  • 29253e7 feat: improved dev setup
  • 6a61c38 feat: install from local in debug
  • 79cfc1d refactor: wranglerjs installation
  • 517b455 Merge pull request #158 from cloudflare/ci-add-wranglerjs-release
  • db52eb1 refactor: wrangler-js > wranglerjs
  • 7536a8a ci: add wranglerjs version in release
  • 0100851 Merge pull request #159 from cloudflare/webpack-preview
  • 5d02b01 ci: move -> mv
  • c0211b9 initial kv namespace support
  • 4b83e99 feat(webpack): implement preview
  • cd97799 ci: fix ArchiveFiles location
  • e57f860 Merge pull request #156 from cloudflare/fix-raw-strings
  • 93760ec ci: try to add wranglerjs release
  • 13ef637 Merge pull request #151 from cloudflare/zoneless
  • 650cd86 fix(webpack): generate valid json
  • 4e2d5ae feat(zoneless): make it happen
  • c2aefbd Merge pull request #146 from cloudflare/subdomain
  • 104ac2d feat(subdomain): add ability to add subdomain
  • fa3bf9b Merge pull request #145 from cloudflare/cleanup
  • 1429916 fix(test): wrangler with no args is not quite success
  • 8644c5c Merge pull request #143 from Electroid/help-with-no-args
  • 9baf675 Merge pull request #144 from cloudflare/webpack-default
  • 7d718d8 fix(lint): friggin allow redundant closures
  • b4b6207 fix(style): remove unecessary format
  • 03c6237 fix(style): unwrap_or -> unwrap_or_else
  • f346160 fix(style): collapsable if/else
  • 3246af5 feat(projecttype): default to webpack
  • 8a1ea86 Merge pull request #142 from cloudflare/type-flag
  • 995771c Show command help when given no arguments
  • b8a49e4 feat(project_type): deserialize lowercase
  • 97b01a6 feat(generate): allow passing type
  • 0c7e728 Merge pull request #141 from cloudflare/no-more-wasm-notice
  • facb753 fix(cli): commands are not wasm specific
  • 9dc2170 Merge pull request #121 from cloudflare/test-this-thing
  • e4346d0 fix(wranglerjs): createdir with path not string, windows support
  • 9323814 fix(wranglerjs): typo
  • 17ff979 Merge pull request #139 from nodebotanist/add-types-to-README
  • 0b929c9 Fixed double colon
  • 45623cd Added type for wrangler.toml file
  • 13712b8 fix(ci): install node
  • 6cad80b Merge pull request #136 from cloudflare/build-command-typo
  • c735132 fix(ci): install cargo gen manually
  • 946f9b1 Merge branch 'master' into test-this-thing
  • a8b7fff feat(cli): only fetch the settings a cmd really needs
  • e25ea8f refactor(settings): split project and user
  • 2a664dc Fix typo in build output for JS projects
  • 3a422e3 fix(settings): s/user/settings
  • d8e80f6 fix(settings): remove account
  • 1f774b0 Merge pull request #131 from cloudflare/test-this-thing2
  • f43091c...
Read more

πŸ’₯ 0.1.1

04 Apr 19:48
Compare
Choose a tag to compare
  • πŸ€• Fixes

    • Fix publish and preview bug for projects with a - - jaysonsantos, issue/36 pull/38

      Rust is a sometimes surprisingly opinionated language! When your Cargo.toml specifies a project
      name with a hypen(-) in the name, the Rust compiler will implicitly understand this as a _ for
      all imports and when it creates compiled artifacts it will name them with a _.

      The original implementation of wrangler skipped over this, and as a result would go looking for a
      wasm file with a - when it should have been looking for a _. This resulted in a bit of a gross
      error message that stated that a file was not found.

      We've fixed this now- so go ahead and name your packages with -s!

  • πŸ“– Documentation

    • Install instructions with OpenSSL troubleshooting notes - AustinCorridor, issue/35 pull/43

      Because of wrangler's use of cargo-generate we use OpenSSL. Classically, this is a tricky
      dependency. Some users may run into issue with it! We've documented the steps to fix it on MacOS-
      if you run into this on other platforms, we'd love a PR!

    • Typo and casing fixes - neynah, pull/42

      First releases almost always have some typos. Now they're fixed!

🌌 0.1.0

04 Apr 19:47
Compare
Choose a tag to compare