@procore/hammer-lib-tsup 0.9.1 → 1.0.1

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # @procore/hammer-lib-tsup
 
+## 1.0.1
+
+### Patch Changes
+
+- 2400f21: Update package runtime dependencies and source updates across Hammer packages.
+- Updated dependencies [2400f21]
+- Updated dependencies [1d23401]
+- Updated dependencies [1d23401]
+  - @procore/hammer-utils@1.0.1
+  - @procore/hammer-types@1.2.0
+
+## 1.0.0
+
+### Major Changes
+
+- d10edb3: First general release. No breaking changes from prior releases.
+
+### Patch Changes
+
+- d6e8e38: Upgrades dependencies.
+- Updated dependencies [d6e8e38]
+- Updated dependencies [d10edb3]
+  - @procore/hammer-utils@1.0.0
+  - @procore/hammer-types@1.0.0
+
 ## 0.9.1
 
 ### Patch Changes

package/README.md

@@ -16,24 +16,54 @@ yarn add -D @procore/hammer-lib-tsup
 
 Custom configuration is done using the `hammer` configuration file. The customization key is `libTsup`, and the configuration that should be returned should be compatible with the tsup `defineConfig` format.
 
-```js
+```ts
+// hammer.config.ts
+
+import { type HammerConfig } from '@procore/hammer-types';
+import '@procore/hammer-lib-tsup';
+
 export default {
-    // NOTE: originalConfig is an array of tsup Options objects:
-    // one for modern configuration, and one for legacy configuration
-    // Please make sure that any customization you do accounts for
-    // both configuration elements.
-    libTsup(originalConfig) {
-        const customizedConfig =
-        // ... mutations, transformations, etc.
-        return customizedConfig;
-    }
-}
+  /**
+   * NOTE: `config` is an array of tsup Options objects:
+   * one for modern configuration, and one for legacy configuration
+   * Please make sure that any customization you do accounts for
+   * both configuration elements.
+   *
+   * config[0] == modern
+   * config[1] == legacy
+   */
+  libTsup(config) {
+    return [
+      {
+        ...config[0],
+        // custom modern config
+      },
+      {
+        ...config[1],
+        // custom legacy config
+      },
+    ];
+  },
+} satisfies HammerConfig;
 ```
 
 **NOTE**: The default configuration should handle nearly all packages. If
 you find that you are doing a lot of customization, or the same change in
 multiple projects, consider reviewing your configuration with the UI Foundations team.
 
+### Using `lib:build --analyze`
+
+When you run `hammer lib:build --analyze`, it generates the following output files:
+
+- `metafile-esm.json`: Metadata for the ESM (ECMAScript Module) output.
+- `metafile-cjs.json`: Metadata for the CJS (CommonJS) output.
+
+These files can be used to analyze the bundle, understand the size of individual modules, and identify optimizations.
+
+For more detailed information on how the metadata works, refer to the [Tsup Metafile Documentation][tsup-metafile].
+
+Additionally, you can use tools like [Bundle Buddy][bundle-buddy] to visualize the output and track down duplicate dependencies or optimize your bundle for better performance.
+
 ## Development
 
 This project uses [`yarn`][yarn], and supports the following commands:
@@ -48,19 +78,6 @@ This project uses [`yarn`][yarn], and supports the following commands:
 - `test:ci`: run the unit test suite, reporting coverage.
 - `lib:build --analyze`: builds the library and generates metadata for bundle analysis.
 
-### Using `lib:build --analyze`
-
-When you run `hammer lib:build --analyze`, it generates the following output files:
-
-- `metafile-esm.json`: Metadata for the ESM (ECMAScript Module) output.
-- `metafile-cjs.json`: Metadata for the CJS (CommonJS) output.
-
-These files can be used to analyze the bundle, understand the size of individual modules, and identify optimizations.
-
-For more detailed information on how the metadata works, refer to the [Tsup Metafile Documentation][tsup-metafile].
-
-Additionally, you can use tools like [Bundle Buddy][bundle-buddy] to visualize the output and track down duplicate dependencies or optimize your bundle for better performance.
-
 [bundle-buddy]: https://www.bundle-buddy.com/esbuild
 [eslint]: https://eslint.org/
 [prettier]: https://prettier.io/

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@procore/hammer-lib-tsup",
-  "version": "0.9.1",
+  "version": "1.0.1",
   "description": "Hammer library builder, tsup-style",
   "author": "Procore Technologies, Inc",
   "homepage": "https://github.com/procore/hammer/packages/lib-tsup",
@@ -51,29 +51,29 @@
     }
   },
   "dependencies": {
-    "@procore/hammer-types": "^0.8.0",
-    "@procore/hammer-utils": "^0.5.0",
+    "@procore/hammer-types": "^1.2.0",
+    "@procore/hammer-utils": "^1.0.1",
     "cli-highlight": "^2.1.11",
-    "esbuild": "^0.25.6",
-    "esbuild-sass-plugin": "^3.3.1",
+    "esbuild": "^0.27.4",
+    "esbuild-sass-plugin": "^3.7.0",
     "pathe": "^2.0.3",
     "picocolors": "^1.1.1",
-    "sass-embedded": "^1.89.2",
-    "tsup": "^8.5.0"
+    "sass-embedded": "^1.98.0",
+    "tsup": "^8.5.1"
   },
   "devDependencies": {
     "@procore/eslint-config": "^15.3.2",
-    "@procore/hammer-test-utils": "^0.3.0",
+    "@procore/hammer-test-utils": "^2.0.0",
     "@procore/prettier-config": "^1.1.1",
     "@procore/typescript-config": "^2.1.0",
-    "@types/node": "^20.19.11",
-    "@vitest/coverage-v8": "^3.2.4",
-    "del-cli": "^6.0.0",
-    "eslint": "^9.33.0",
-    "postcss": "^8.5.6",
-    "prettier": "^3.6.2",
-    "strip-ansi": "^7.1.0",
+    "@types/node": "^20.19.37",
+    "@vitest/coverage-v8": "^4.1.2",
+    "del-cli": "^7.0.0",
+    "eslint": "^9.39.4",
+    "postcss": "^8.5.8",
+    "prettier": "^3.8.1",
+    "strip-ansi": "^7.2.0",
     "typescript": "~5.5.4",
-    "vitest": "^3.2.4"
+    "vitest": "^4.1.2"
   }
 }