@tryretool/custom-component-support v1.4.0

Custom component support

Visit our documentation at retool.com for more information.

Changelog

v1.4.0

• Added the ability to provide custom headers to send with HTTP requests from npx retool-ccl. All commands now accept a --header option, which will take the subsequent string, and send it as a header in all HTTP requests sent by the CLI. --header can be repeated many times, to include multiple headers. For example, npx retool-ccl deploy --header 'header-1: value-1' --header 'header-2: value-2' will send those two headers with each HTTP request. While running npx retool-ccl sync, use the --target-header option for headers to use when sending HTTP requests to the target instance of the sync command, and --header for headers for the origin instance.

v1.3.0

• Only one user can update a dev revision at time. This update makes npx retool-ccl dev automatically retry up to 5 times if a conflict in updating the dev revision is detected.

v1.2.0

Retool.useStateNumber({
      name: "someNumber",
      initialValue: -5.2
})

• Fixes a bug where when an error would occur when giving negative numbers for a piece of custom component state (eg: the above example use of useStateNumber would fail during build, when it should succeed. It now succeeds)

v1.1.0

• Added support for --skip-updates-check option. Normally, running any commands from the custom-component-support library will trigger a check of npmjs.com to see if newer version of custom-component-support exist. Passing this option prevents these checks from happening.
• Correctly prints an error message if a cloud user reaches their storage limit for custom component code bundles, and is unable to deploy new revisions.

v0.0.18

• When using dev mode, avoids sending source maps for any dependencies in node_modules. Dev mode continues to send source maps for all other code.

v0.0.17

• Fix npx commands, so that they return non-zero exit codes on errors.

v0.0.16

• Adds a "build" command, which will build code without deploying it to a Retool instance. Can be run via either npx retool-ccl deploy --dry-run/-n or npx retool-ccl build.