@tryretool/custom-component-support
v1.2.0
Published
Visit our documentation at [retool.com](https://docs.retool.com/apps/web/guides/components/custom-components-beta) for more information.
Downloads
946
Keywords
Readme
Custom component support
Visit our documentation at retool.com for more information.
Changelog
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
ornpx retool-ccl build
.