@theme-ui/css - npm Package Compare versions

Comparing version 0.15.0-develop.26 to 0.15.0-develop.27

dist/theme-ui-css.cjs.d.ts

@@ -1,11 +0,1 @@
-// are you seeing an error that a default export doesn't exist but your source file has a default export?
-// you should run `yarn` or `yarn preconstruct dev` if preconstruct dev isn't in your postinstall hook
-
-// curious why you need to?
-// this file exists so that you can import from the entrypoint normally
-// except that it points to your source file and you don't need to run build constantly
-// which means we need to re-export all of the modules from your source file
-// and since export * doesn't include default exports, we need to read your source file
-// to check for a default export and re-export it if it exists
-// it's not ideal, but it works pretty well ¯\_(ツ)_/¯
-export * from "../src/index";
+export * from "./declarations/src/index";

dist/theme-ui-css.cjs.js

@@ -1,16 +0,7 @@
-"use strict";
-// this file might look strange and you might be wondering what it's for
-// it's lets you import your source files by importing this entrypoint
-// as you would import it if it was built with preconstruct build
-// this file is slightly different to some others though
-// it has a require hook which compiles your code with Babel
-// this means that you don't have to set up @babel/register or anything like that
-// but you can still require this module and it'll be compiled
+'use strict';
 
-// this bit of code imports the require hook and registers it
-let unregister = require("../../../node_modules/.pnpm/@preconstruct+hook@0.4.0/node_modules/@preconstruct/hook").___internalHook(typeof __dirname === 'undefined' ? undefined : __dirname, "../../..", "..");
-
-// this re-exports the source file
-module.exports = require("../src/index.ts");
-
-unregister();
+if (process.env.NODE_ENV === "production") {
+  module.exports = require("./theme-ui-css.cjs.prod.js");
+} else {
+  module.exports = require("./theme-ui-css.cjs.dev.js");
+}

package.json

 {
   "name": "@theme-ui/css",
-  "version": "0.15.0-develop.26",
+  "version": "v0.15.0-develop.27",
   "source": "src/index.ts",
@@ -23,3 +23,3 @@ "main": "dist/theme-ui-css.cjs.js",
     "@babel/core": "^7",
-    "@theme-ui/test-utils": "^0.15.0-develop.26"
+    "@theme-ui/test-utils": "^v0.15.0-develop.27"
   },
@@ -26,0 +26,0 @@ "preconstruct": {

utils/dist/theme-ui-css-utils.cjs.d.ts

@@ -1,11 +0,1 @@
-// are you seeing an error that a default export doesn't exist but your source file has a default export?
-// you should run `yarn` or `yarn preconstruct dev` if preconstruct dev isn't in your postinstall hook
-
-// curious why you need to?
-// this file exists so that you can import from the entrypoint normally
-// except that it points to your source file and you don't need to run build constantly
-// which means we need to re-export all of the modules from your source file
-// and since export * doesn't include default exports, we need to read your source file
-// to check for a default export and re-export it if it exists
-// it's not ideal, but it works pretty well ¯\_(ツ)_/¯
-export * from "../../src/utils";
+export * from "../../dist/declarations/src/utils";

utils/dist/theme-ui-css-utils.cjs.js

@@ -1,16 +0,7 @@
-"use strict";
-// this file might look strange and you might be wondering what it's for
-// it's lets you import your source files by importing this entrypoint
-// as you would import it if it was built with preconstruct build
-// this file is slightly different to some others though
-// it has a require hook which compiles your code with Babel
-// this means that you don't have to set up @babel/register or anything like that
-// but you can still require this module and it'll be compiled
+'use strict';
 
-// this bit of code imports the require hook and registers it
-let unregister = require("../../../../node_modules/.pnpm/@preconstruct+hook@0.4.0/node_modules/@preconstruct/hook").___internalHook(typeof __dirname === 'undefined' ? undefined : __dirname, "../../../..", "../..");
-
-// this re-exports the source file
-module.exports = require("../../src/utils.ts");
-
-unregister();
+if (process.env.NODE_ENV === "production") {
+  module.exports = require("./theme-ui-css-utils.cjs.prod.js");
+} else {
+  module.exports = require("./theme-ui-css-utils.cjs.dev.js");
+}

New alerts

Manifest confusion

Supply chain risk

This package has inconsistent metadata. This could be malicious or caused by an error when publishing the package.

Found 1 instance in 1 package

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

159620

increased by84.79%

Number of package files

27

increased by58.82%

Lines of code

4290

increased by96.25%

Worsened metrics

Number of low supply chain risk alerts

3

increased by200%

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes