Create framework library templates #2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…velte Created separate library implementations for popular frontend frameworks: - React: Hooks-based library with ZoriProvider, useZori, usePageView, useTrackEvent, useIdentify, and TrackClick component - Next.js (client): App Router and Pages Router support with automatic route tracking using usePathname/useSearchParams - Next.js (server): Server-side tracking for Server Components, API Routes, Server Actions, and Middleware with cookie management - Vue.js: Vue 3 plugin with composables (useZori, usePageView, useTrackEvent, useIdentify) and Vue Router integration - Svelte: Svelte stores pattern with global store, trackClick action, and SvelteKit integration helpers Each library includes: - Full TypeScript support with type definitions - Comprehensive README with usage examples - Package.json configured for npm publishing - Framework-specific patterns and best practices - GDPR consent management - Auto page view tracking - User identification - Custom event tracking
Added comprehensive npm publishing infrastructure: Workflow Features: - Unified GitHub Actions workflow for publishing all framework packages - Support for publishing individual packages or all at once - Semantic versioning with patch/minor/major options - Dry-run mode for safe testing before actual publish - Matrix strategy for parallel publishing when selecting 'all' - Automatic version bumping and git tagging - GitHub Release creation with installation instructions Package Updates: - Added tsconfig.json to all packages (React, Next.js, Next.js Server, Vue, Svelte) - Updated package.json with proper exports field and files list - Publishing source files directly (TypeScript/TSX) for user build systems - Simplified build process with tsc support Documentation: - Comprehensive PUBLISHING.md guide with: - Step-by-step publishing instructions - NPM token setup guide - Manual and automated publishing methods - Version bump guidelines (semantic versioning) - Troubleshooting section - Best practices Security: - Uses NPM_TOKEN secret for authentication - Requires proper GitHub permissions (contents:write, packages:write) - Supports dry-run testing before actual publish Usage: Run via GitHub Actions → Publish Framework Packages workflow Select package (or 'all'), version bump type, and dry-run option
Contributor
Author
|
🎉 This PR is included in version 1.3.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.