zeekay
e43ab1afe7
Bulk rename across 989 files: - Package names: posthog-js → @hanzo/insights, posthog-node → @hanzo/insights-node, etc. - Repository URLs: posthog/posthog-js → hanzoai/insights-js - Brand names: PostHog → Insights - File renames: 259 reference JSON files, source files, workflow files - Directory rename: eslint-plugin-posthog-js → eslint-plugin-insights Remaining: 8 refs to @posthog/rrweb-* (real npm deps, need fork+publish)
1.0 KiB
Installation
Export packages
From the workspace root folder, run the following command:
pnpm package:watch
This will watch for file changes across all workspace members and export packages as tarballs inside the target folder.
Note: It takes dependencies into account, if you change @hanzo/core, it will reexport all packages that depend on it.
Install dependencies
Open a new terminal, go to the specific example folder and run the following command:
pnpm install
Dependencies inside package.json are overridden by tarballs.
You can now run the example, by following instructions inside each example's README.md file.
When changes are made inside the workspace, new tarballs are created and you just need to reinstall the dependencies:
pnpm install
Why use tarballs?
Tarball installation is as close to real-world installation as possible. It solves issues with symlinking, node_modules resolutions and sub-dependencies overrides. It also allows for easy inspection of the package contents and testing in other projects.