@formo/analytics 1.17.2 → 1.17.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@formo/analytics",
-  "version": "1.17.2",
+  "version": "1.17.4",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/getformo/sdk.git"
@@ -9,6 +9,9 @@
   "types": "dist/esm/src/index.d.ts",
   "module": "dist/esm/src/index.js",
   "unpkg": "dist/index.umd.min.js",
+  "files": [
+    "dist"
+  ],
   "exports": {
     ".": {
       "import": "./dist/esm/src/index.js",

package/.env.example

@@ -1 +0,0 @@
-REACT_APP_HIGHLIGHT_PROJECT_ID = 

package/.github/workflows/ci.yml

@@ -1,50 +0,0 @@
-name: Formo SDK CI Check
-
-on:
-  push:
-    branches-ignore: [main]
-  pull_request:
-    branches:
-      - main
-
-permissions:
-  contents: read
-  pages: write
-  id-token: write
-
-concurrency:
-  group: "pages"
-  cancel-in-progress: false
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-      - name: Detect package manager
-        id: detect-package-manager
-        run: |
-          if [ -f "${{ github.workspace }}/yarn.lock" ]; then
-            echo "manager=yarn" >> $GITHUB_OUTPUT
-            echo "command=install" >> $GITHUB_OUTPUT
-            echo "runner=yarn" >> $GITHUB_OUTPUT
-            exit 0
-          elif [ -f "${{ github.workspace }}/package.json" ]; then
-            echo "manager=npm" >> $GITHUB_OUTPUT
-            echo "command=ci" >> $GITHUB_OUTPUT
-            echo "runner=npx --no-install" >> $GITHUB_OUTPUT
-            exit 0
-          else
-            echo "Unable to determine package manager"
-            exit 1
-          fi
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version: "20"
-          cache: ${{ steps.detect-package-manager.outputs.manager }}
-      - name: Install dependencies
-        run: ${{ steps.detect-package-manager.outputs.manager }} ${{ steps.detect-package-manager.outputs.command }}
-      - name: Build SDK
-        run: ${{ steps.detect-package-manager.outputs.runner }} build

package/.github/workflows/release.yml

@@ -1,54 +0,0 @@
-name: Release package
-
-# Runs when a PR to main is merged, main branch is protected, so that only PRs to main are merged
-on:
-  push:
-    branches:
-      - main
-
-jobs:
-  release:
-    permissions:
-      contents: write
-      issues: write
-      pull-requests: write
-      id-token: write
-
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-      - name: Detect package manager
-        id: detect-package-manager
-        run: |
-          if [ -f "${{ github.workspace }}/yarn.lock" ]; then
-            echo "manager=yarn" >> $GITHUB_OUTPUT
-            echo "command=install" >> $GITHUB_OUTPUT
-            echo "build_command=build" >> $GITHUB_OUTPUT
-            echo "runner=yarn" >> $GITHUB_OUTPUT
-            exit 0
-          elif [ -f "${{ github.workspace }}/package.json" ]; then
-            echo "manager=npm" >> $GITHUB_OUTPUT
-            echo "command=ci" >> $GITHUB_OUTPUT
-            echo "build_command=run build" >> $GITHUB_OUTPUT
-            echo "runner=npx --no-install" >> $GITHUB_OUTPUT
-            exit 0
-          else
-            echo "Unable to determine package manager"
-            exit 1
-          fi
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version: "20"
-          cache: ${{ steps.detect-package-manager.outputs.manager }}
-      - name: Install dependencies
-        run: ${{ steps.detect-package-manager.outputs.manager }} ${{ steps.detect-package-manager.outputs.command }}
-      - name: Build SDK
-        run: ${{ steps.detect-package-manager.outputs.manager }} ${{ steps.detect-package-manager.outputs.build_command }}
-      - name: Release
-        run: ${{ steps.detect-package-manager.outputs.runner }} semantic-release
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          GH_RELEASE_TOKEN: ${{ secrets.GH_RELEASE_TOKEN }}
-          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

package/.husky/post-commit

@@ -1,7 +0,0 @@
-#!/bin/sh
-. "$(dirname "$0")/_/husky.sh"
-
-echo "✅ Commit completed successfully!"
-
-# Run size-limit
-npx size-limit

package/.husky/pre-commit

@@ -1,11 +0,0 @@
-#!/bin/sh
-. "$(dirname "$0")/_/husky.sh"
-
-echo "Running pre-commit process..."
-
-npm run build
-
-npx genversion --esm --semi src/lib/version.ts
-
-# Add modified files to Git staging
-git add .

package/.releaserc.js

@@ -1,34 +0,0 @@
-module.exports = {
-  branches: ["main"],
-  plugins: [
-    [
-      "@semantic-release/commit-analyzer",
-      {
-        preset: "conventionalcommits",
-      },
-    ],
-    "@semantic-release/release-notes-generator",
-    "@semantic-release/npm",
-    // Uncomment if you want to commit version bump to package.json
-    // [
-    //   "@semantic-release/git",
-    //   {
-    //     assets: ["package.json", "package-lock.json"],
-    //     message: "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}",
-    //   },
-    // ],
-    [
-      "@semantic-release/github",
-      {
-        assets: ["dist"],
-        addReleases: "bottom",
-      },
-    ],
-    [
-      "@semantic-release/exec",
-      {
-        successCmd: "scripts/generate-sri.sh ${nextRelease.version}",
-      },
-    ],
-  ],
-};

package/CONTRIBUTING.md

@@ -1,83 +0,0 @@
-# Development Guide
-
-If you want to contribute or run a local version of the Formo Analytics SDK, follow these steps:
-
-### Build the SDK Locally
-
-Run the following command to build both CommonJS and ESM versions of the SDK:
-
-```jsx
-yarn build-cjs && yarn build-esm && yarn webpack --mode=production
-```
-
-or if you're using NPM:
-
-```jsx
-npm run build
-```
-
-### Testing locally
-
-1. Link the local package to your project
-
-> See [this guide](https://dev.to/one-beyond/different-approaches-to-testing-your-own-packages-locally-npm-link-4hoj) on how to use `npm link` or [this guide](https://classic.yarnpkg.com/lang/en/docs/cli/link/) for `yarn link` to test the package locally.
-
-For example, if I want to test the package with a project that is in the same directory:
-
-```
-~/
-├── formo-analytics-example-next/
-└── sdk/
-```
-
-Run the following command:
-
-```bash
-# ~/formo-analytics-example-next
-npm link ../sdk
-OR
-yarn link ../sdk
-```
-
-Any changes you make to your local package will be reflected in the project you linked it to.
-However, you have to run `build` to apply the changes you made to the local package:
-
-```
-# ~/sdk
-npm run build
-```
-
-The new change will be reflected in the project you linked it to.
-
-To unlink the package, run the following command:
-
-```bash
-# In ~/formo-analytics-example-next
-npm unlink ../sdk
-OR
-yarn unlink ../sdk
-```
-
-## Troubleshooting
-
-- Remove your `node_modules` and `yarn link` and run `yarn link` and `yarn install` again.
-- Try running `yarn build` in the SDK directory to ensure the changes are applied.
-- Try running `yarn unlink` and `yarn link` again.
-
-# Commit message format
-
-**semantic-release** uses the commit messages to determine the consumer impact of changes in the codebase.
-Following formalized conventions for commit messages, **semantic-release** automatically determines the next [semantic version](https://semver.org) number, generates a changelog and publishes the release.
-
-By default, **semantic-release** uses [Angular Commit Message Conventions](https://github.com/angular/angular/blob/main/contributing-docs/commit-message-guidelines.md).
-The commit message format can be changed with the [`preset` or `config` options](docs/usage/configuration.md#options) of the [@semantic-release/commit-analyzer](https://github.com/semantic-release/commit-analyzer#options) and [@semantic-release/release-notes-generator](https://github.com/semantic-release/release-notes-generator#options) plugins.
-
-Tools such as [commitizen](https://github.com/commitizen/cz-cli) or [commitlint](https://github.com/conventional-changelog/commitlint) can be used to help contributors and enforce valid commit messages.
-
-The table below shows which commit message gets you which release type when `semantic-release` runs (using the default configuration):
-
-| Commit message                                                                                                                                                                                   | Release type                                                                                                    |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------- |
-| `fix(pencil): stop graphite breaking when too much pressure applied`                                                                                                                             | ~~Patch~~ Fix Release                                                                                           |
-| `feat(pencil): add 'graphiteWidth' option`                                                                                                                                                       | ~~Minor~~ Feature Release                                                                                       |
-| `perf(pencil): remove graphiteWidth option`<br><br>`BREAKING CHANGE: The graphiteWidth option has been removed.`<br>`The default graphite width of 10mm is always used for performance reasons.` | ~~Major~~ Breaking Release <br /> (Note that the `BREAKING CHANGE: ` token must be in the footer of the commit) |

package/scripts/generate-sri.sh

@@ -1,52 +0,0 @@
-#!/bin/bash
-set -e
-
-VERSION=$1
-REPO="getformo/sdk"
-FILE="dist/index.umd.min.js"
-PACKAGE_NAME="@formo/analytics"
-
-# Get the tarball from unpkg and compute SRI
-URL="https://unpkg.com/${PACKAGE_NAME}@${VERSION}/${FILE}"
-echo "Fetching: $URL"
-HASH=$(curl -sSL --compressed "$URL" | openssl dgst -sha384 -binary | openssl base64 -A)
-
-SNIPPET=$(cat <<EOF
-<script 
-  src="https://unpkg.com/${PACKAGE_NAME}@${VERSION}/${FILE}"
-  integrity="sha384-${HASH}"
-  crossorigin="anonymous"
-></script>
-EOF
-)
-
-# Get the release ID from GitHub API
-RELEASE_ID=$(curl -s -H "Authorization: Bearer $GH_RELEASE_TOKEN" \
-  https://api.github.com/repos/${REPO}/releases/tags/v${VERSION} \
-  | jq -r '.id')
-
-# Fetch current body
-CURRENT_BODY=$(curl -s -H "Authorization: Bearer $GH_RELEASE_TOKEN" \
-  https://api.github.com/repos/${REPO}/releases/$RELEASE_ID \
-  | jq -r '.body')
-
-# Append SRI snippet
-UPDATED_BODY=$(cat <<EOF
-${CURRENT_BODY}
-
-🔒 **Subresource Integrity Snippet**
-
-\`\`\`html
-${SNIPPET}
-\`\`\`
-EOF
-)
-
-# Patch the release body
-curl -s -X PATCH \
-  -H "Authorization: Bearer $GH_RELEASE_TOKEN" \
-  -H "Content-Type: application/json" \
-  -d "$(jq -n --arg body "$UPDATED_BODY" '{body: $body}')" \
-  https://api.github.com/repos/${REPO}/releases/$RELEASE_ID
-
-echo "✅ GitHub Release updated with SRI snippet."