check-side-effects - npm Package Compare versions

Comparing version 0.0.13 to 0.0.14

dist/tslint/noToplevelPropertyAccessRule.js

dist/tslint/noToplevelPropertyAccessRule.js.map

package.json

		{
		"name": "check-side-effects",
		"version": "0.0.13",
		"version": "0.0.14",
		"description": "Check if a ES module has side effects.",
		@@ -25,9 +25,10 @@ "repository": "https://github.com/filipesilva/check-side-effects",
		"rollup-plugin-terser": "~4.0.4",
		"tslib": "~1.9.3"
		"tslib": "~1.9.3",
		"tslint": "^5.16.0",
		"typescript": "^3.4.5"
		},
		"devDependencies": {
		"@types/minimist": "~1.2.0",
		"@types/terser": "~3.8.0",
		"typescript": "~3.2.4"
		"@types/terser": "~3.8.0"
		}
		}

README.md

		@@ -128,1 +128,28 @@ # Check side effects
		```

		## TSLint rules

		Included you can find a [TSLint](https://palantir.github.io/tslint/) rule to detect toplevel property access.

		You can use it by adding the path below to `rulesDirectory` and the `no-toplevel-property-access` rule. Path fragments to include are optional and, if omitted, all TS files will be checked.

		```json
		{
		"rulesDirectory": [
		"node_modules/check-side-effects/dist/tslint"
		],
		"rules": {
		"no-toplevel-property-access": [
		true,
		"/path/fragments/to/include/",
		"/another/path/fragment/to/include/"
		]
		}
		}
		```

		## Developing on this repository

		To build, run `npm run build`. To test, run `npm run test`.

		To release, run `npm run release <release-type>` where `<release-type>` is one of `patch`, `minor` or `major`.

New alerts