pure-index - npm Package Compare versions

Comparing version 0.0.57 to 1.0.0-next.0

package.json

 {
   "name": "pure-index",
   "type": "module",
-  "version": "0.0.57",
+  "version": "1.0.0-next.0",
   "description": "Utility for monorepos. It helps to clean your packages of unused exports with ease",
@@ -14,4 +14,5 @@ "main": "./dist/api/index.js",
   "scripts": {
-    "build": "rm -rf ./dist && tsc --project ./tsconfig.build.json && tsc-alias",
-    "prepublishOnly": "npm t && npm run build",
+    "build": "make build",
+    "prepublishOnly": "make prepublishOnly",
+    "prettier:check": "make prettierCheck",
     "test": "vitest"
@@ -18,0 +19,0 @@ },

README.md

 # 🌿 Pure Index
 
-Pure Index is utility for packages. It helps to clean your packages of unused exports with ease.<br />And it's also very fast ⚡️
+Pure Index is a tool for packages. It helps to clean your packages of unused exports with ease.<br />
+And it’s also speedy ⚡️
 
@@ -9,3 +10,3 @@ ## Motivation
 
-```ts title="ui-kit/index.ts"
+```ts title="ui-kit/src/index.ts"
 export { Button } from './components/button';
@@ -18,5 +19,5 @@ export { Text } from './components/text';
 
-All of its exportable code requires support. But is all of it actually being used?
+The number of exports increases over time. All of its exportable code requires support. But is all of it being used?
 
-You can check this manually by just looping through the exports. It's time consuming and there is a chance of error. What if it's code is used by multiple repositories?
+You can check this manually by just looping through the exports. It’s time-consuming, and there is a chance of error. What if multiple repositories use its code?
 
@@ -35,5 +36,5 @@ Let's automate this process!
 
-Pure Index can be used either through a [command line interface](https://space307.github.io/pure-index/intro/cli) with an optional [configuration file](https://space307.github.io/pure-index/reference/configuration), or else through its [JavaScript API](https://space307.github.io/pure-index/intro/js-api).
+Pure Index can be used either through a [command line interface](https://space307.github.io/pure-index/intro/cli) with an optional [configuration file](https://space307.github.io/pure-index/reference/configuration) or its [JavaScript API](https://space307.github.io/pure-index/intro/js-api).
 
-1. Add the `check-exports` script in the `package.json` of each package that needs to be checked
+1. Add the `check-exports` script in the `package.json` of packages that require checking.
 
@@ -56,2 +57,2 @@ ```diff
 
-For additional information, guides and api reference visit [our documentation site](https://space307.github.io/pure-index)
+Visit [our documentation site](https://space307.github.io/pure-index) for additional information, guides, and API references..

New alerts

Empty package

Supply chain risk

Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.

Found 1 instance in 1 package

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

Improved metrics

Number of lines in readme file

55

increased by1.85%

Worsened metrics

Total package byte prevSize

4798

decreased by-81.96%

Number of package files

4

decreased by-90.48%

Lines of code

0

decreased by-100%

Number of medium supply chain risk alerts

2

increased byInfinity%

No dependency changes