@cloudflare/component-box - npm Package Compare versions

Comparing version 1.0.4 to 1.0.5

CHANGELOG.md

		@@ -6,2 +6,10 @@ # Change Log

		<a name="1.0.5"></a>
		## [1.0.5](http://stash.cfops.it:7999/www/cf-ux/compare/@cloudflare/component-box@1.0.4...@cloudflare/component-box@1.0.5) (2018-05-24)




		Note: Version bump only for package @cloudflare/component-box

		<a name="1.0.4"></a>
		@@ -8,0 +16,0 @@ ## [1.0.4](http://stash.cfops.it:7999/www/cf-ux/compare/@cloudflare/component-box@1.0.3...@cloudflare/component-box@1.0.4) (2018-05-24)

package.json

		{
		"name": "@cloudflare/component-box",
		"description": "Cloudflare Box Component\n\nThis is styling component similar to cf-component-flex which allows for arbitrary styling.\n\n This component should only be used when the built in style doesn't quite fit the bill and when it can't be done with fela. Ideally, cfui components should have the right styling built in for most cases. In the few edge cases that pop up in real world feature development, this is an alternative to wrapping your component in a `<div>` or `<span>` and styling it with css to accomodate one-offs. \n\n Also, note that using Box effectively performs a component level CSS reset, as all props not provided will be pulled from the default theme. These defaults, outlined in propertiesSpec, either match the browser defaults, or are taken from our global styles as defined by cf-style-const.",
		"version": "1.0.4",
		"version": "1.0.5",
		"main": "lib/index.js",
		@@ -15,4 +15,4 @@ "module": "es/index.js",
		"dependencies": {
		"@cloudflare/style-const": "^1.0.4",
		"@cloudflare/style-container": "^1.0.4",
		"@cloudflare/style-const": "^1.0.5",
		"@cloudflare/style-container": "^1.0.5",
		"polished": "^1.9.2",
		@@ -19,0 +19,0 @@ "prop-types": "^15.6.0"

New alerts