@sketch-hq/sketch-assistant-types - npm Package Compare versions

CHANGELOG.md

		# @sketch-hq/sketch-assistant-types

		## 3.0.0-next.5

		### Minor Changes

		- 7f1ef34: New function types for style equality comparison were added to the RuleUtils type

		## 3.0.0-next.4

		## 4.0.1-next.8
		### Patch Changes

		- 111b641: Fix AssistantPackageExport type to handle Assistants that may be exported as ES Modules
		at the top level

		## 3.0.0-next.3

		### Patch Changes

		- c0d835b: Make package public
		- 98abfc9: Add `ruleTitle` as an official reserved rule option name

		## 3.0.0-next.2

		### Minor Changes

		- d696d99: Allow rule titles and descriptions to interpolate config values.

		## 3.0.0-next.1

		### Patch Changes

		- 8aa3b4a: Include rule name in Assistant RunResult metadata

		## 3.0.0-next.0

		### Major Changes

		- d90b967: Remove config-level ignore options `ignoreNames` and `ignoreClasses`.

		## 2.0.1

		### Patch Changes

		- 0aeb5e7: Rename Assistant package.json config property to `sketch-assistant`

		## 2.0.0

		### Major Changes

		- 8d16965: Add type for Assistant package.json and move Assistant title and description properties
		to it

		### Patch Changes

		- fb8190d: Update to `@sketch-hq/sketch-file-format-ts@4.0.3`

		## 1.0.0

		### Major Changes

		- 50dc9d6: Initial release
		- bc13811: Initial release in monorepo.

dist/types.js

		@@ -23,2 +23,1 @@ "use strict";
		})(ReservedRuleOptionNames = exports.ReservedRuleOptionNames \|\| (exports.ReservedRuleOptionNames = {}));
		//# sourceMappingURL=types.js.map

package.json

		{
		"name": "@sketch-hq/sketch-assistant-types",
		"version": "3.0.0-next.5",
		"version": "4.0.1-next.8",
		"main": "dist/types",
		@@ -8,3 +8,3 @@ "types": "dist/types",
		"license": "MIT",
		"repository": "github:sketch-hq/sketch-assistant-types",
		"repository": "github:sketch-hq/sketch-assistants",
		"keywords": [
		@@ -18,5 +18,4 @@ "sketch",
		"scripts": {
		"build": "rm -rf ./dist && tsc --project tsconfig.pkg.json",
		"format-check": "prettier --check {.json,.md,src/*.ts}",
		"release": "yarn build && changeset publish"
		"build": "tsc",
		"test": "echo \"Not implemented\""
		},
		@@ -28,8 +27,3 @@ "files": ["dist"],
		"@types/json-schema": "7.0.4"
		},
		"devDependencies": {
		"@changesets/cli": "2.6.2",
		"prettier": "2.0.4",
		"typescript": "3.8.3"
		}
		}

README.md

		@@ -13,33 +13,1 @@ # sketch-assistant-types
		```

		> ⚠️ The package is in pre-release mode using the `next` tag.

		## Development

		This section of the readme is related to developing the package. If you just want to consume the
		package you can safely ignore this.

		### Scripts

		\| Script \| Description \|
		\| ----------------- \| ----------------------------------- \|
		\| yarn build \| Builds package to `dist` \|
		\| yarn format-check \| Checks the formatting with prettier \|

		### Workflows

		#### Conventional commits

		Try and use the [conventional commits](https://www.conventionalcommits.org/) convention when writing
		commit messages.

		#### Releases

		This repo uses [Atlassian Changesets](https://github.com/atlassian/changesets) to automate the npm
		release process. Read the docs for more information, but the top-level summary is:

		- A GitHub Action maintains a permanently open PR that when merged will publish the package to npm
		with the latest changes and an automatically determined semver
		- If the work you do in a PR should affect the next release, then you need to commit a "changeset"
		to the repo together with the rest of your code changes - do this by running `yarn changeset`.
		You'll be asked to provide a change type (major, minor or patch) and a message

dist/types.js.map

New alerts