mixpanel-react-native 3.1.2 → 3.1.3

package/.github/copilot-instructions-guide.md

@@ -1,259 +0,0 @@
-# GitHub Copilot Instructions Integration Guide
-
-This guide explains how GitHub Copilot instructions complement the Claude Code context and Cursor rules to create a comprehensive AI coding assistant ecosystem for the Mixpanel React Native library.
-
-## 🎯 Three-System Architecture
-
-### System Purposes
-```
-┌─────────────────────┐    ┌─────────────────────┐    ┌─────────────────────┐
-│   Claude Code       │    │   Cursor Rules      │    │ Copilot Instructions│
-│   (Knowledge)       │    │   (Behavior)        │    │   (Generation)      │
-├─────────────────────┤    ├─────────────────────┤    ├─────────────────────┤
-│ • Comprehensive     │    │ • Active guidance   │    │ • Persistent        │
-│   documentation     │    │ • Pattern           │    │   reminders         │
-│ • Historical        │    │   enforcement       │    │ • Generation        │
-│   context           │    │ • Context-sensitive │    │   standards         │
-│ • Deep architecture │    │   rules             │    │ • Project           │
-│   understanding     │    │ • Real-time         │    │   personality       │
-│ • Workflow guides   │    │   validation        │    │ • Core patterns     │
-└─────────────────────┘    └─────────────────────┘    └─────────────────────┘
-         │                           │                           │
-         └────────────────┬──────────────────┬────────────────────┘
-                          │                  │
-                 ┌─────────────────────────────────┐
-                 │     Unified AI Assistant        │
-                 │      Effectiveness              │
-                 └─────────────────────────────────┘
-```
-
-## 📋 Instruction File Organization
-
-### Core Instructions (`.github/copilot-instructions.md`)
-**Purpose**: Essential patterns present in every interaction (400 lines)
-**Contents**:
-- Dual implementation strategy (native + JavaScript fallback)
-- Token-based multi-tenancy (fundamental to every operation)
-- Error handling patterns (StringHelper/ObjectHelper validation)
-- Basic naming conventions and architectural principles
-- Platform-specific code patterns (iOS Swift, Android Java)
-
-### Specialized Instructions (`.github/instructions/`)
-**Purpose**: Task-specific guidance that extends core patterns
-
-#### `native-bridge.instructions.md`
-- **Applies to**: `ios/**/*.swift`, `android/**/*.java`, `**/*Native*.js`
-- **Focus**: React Native bridge patterns, @objc/@ReactMethod requirements
-- **Complements**: Core instructions with platform-specific details
-
-#### `test-generation.instructions.md`
-- **Applies to**: `**/*.test.*`, `**/*.spec.*`, `__tests__/**`
-- **Focus**: Dual-mode testing, comprehensive validation patterns
-- **Complements**: Core instructions with testing-specific guidance
-
-#### `storage-patterns.instructions.md`
-- **Applies to**: `**/*storage*.js`, `**/*persistent*.js`, `**/*queue*.js`
-- **Focus**: AsyncStorage abstraction, persistence management
-- **Complements**: Core instructions with storage-specific patterns
-
-### Prompt Files (`.github/prompts/`)
-**Purpose**: Transform complex workflows into reusable Copilot prompts
-
-#### `add-feature.prompt.md`
-- **Mode**: Agent mode with codebase and terminal tools
-- **Purpose**: Step-by-step feature addition workflow
-- **Usage**: Complex multi-file changes requiring coordination
-
-#### `debug-issue.prompt.md`
-- **Mode**: Agent mode with codebase and terminal tools  
-- **Purpose**: Systematic debugging approach
-- **Usage**: Complex issue investigation and resolution
-
-#### `implement-tests.prompt.md`
-- **Mode**: Agent mode with codebase and terminal tools
-- **Purpose**: Comprehensive test suite creation
-- **Usage**: Complete testing workflow for new features
-
-## 🔄 How Instructions Complement Other Tools
-
-### Relationship with Claude Code Context
-
-**Claude Code Provides**:
-- Comprehensive architecture documentation (`claude/architecture/system-design.md`)
-- Detailed pattern explanations (`claude/discovered-patterns.md`)
-- Complete workflow guides (`claude/workflows/*.md`)
-- Historical context and motivation behind decisions
-
-**Copilot Instructions Extract**:
-- Essential patterns for immediate generation guidance
-- Core architectural principles that apply to every file
-- Basic conventions that should be persistent
-- Platform-specific code templates
-
-**Integration Strategy**:
-```
-Claude Code (Deep Reference) → Copilot Instructions (Persistent Guidance)
-    │                                        │
-    ├─ WHY patterns exist                   ├─ WHAT to generate
-    ├─ HOW systems work together            ├─ WHEN to apply patterns  
-    ├─ WHERE to find detailed docs          ├─ HOW to structure code
-    └─ WHEN to use each approach            └─ WHICH conventions to follow
-```
-
-### Relationship with Cursor Rules
-
-**Cursor Rules Provide**:
-- File-pattern based active guidance (`.cursor/rules/components/*.mdc`)
-- Context-sensitive enforcement (auto-attached by file globs)
-- Categorical behavioral rules (always/components/workflows)
-- Real-time pattern validation
-
-**Copilot Instructions Provide**:
-- Always-present core guidance (persistent across all interactions)
-- Generation-focused standards (how to write code)
-- Project personality (make Copilot "know" the project)
-- Essential patterns that can't wait for context activation
-
-**Integration Strategy**:
-```
-Cursor Rules (Contextual) + Copilot Instructions (Persistent) = Complete Guidance
-    │                                        │
-    ├─ Activates based on file patterns     ├─ Always present in every interaction
-    ├─ Specific to current context          ├─ Fundamental to all contexts
-    ├─ Enforces detailed patterns           ├─ Reminds of core principles
-    └─ Comprehensive rule sets              └─ Focused essential guidance
-```
-
-## 🎯 When to Use Each Instruction Type
-
-### Core Instructions (Always Active)
-**Use for**:
-- Patterns that apply to literally every file in the project
-- Fundamental architectural concepts (dual implementation)
-- Non-negotiable conventions (token-based architecture)
-- Basic error handling and validation patterns
-
-**Examples**:
-- Every operation must include token as first parameter
-- All functions use verb-first naming (track, flush, identify)
-- Storage errors must not crash the app (silent failure pattern)
-- Input validation using StringHelper/ObjectHelper classes
-
-### Specialized Instructions (Context-Activated)
-**Use for**:
-- Patterns specific to certain file types or technologies
-- Detailed implementation guidance for specific contexts
-- Extended patterns that build on core instructions
-
-**Examples**:
-- iOS Swift bridge patterns (only for iOS files)
-- Test generation strategies (only for test files)
-- Storage abstraction details (only for storage-related files)
-
-### Prompt Files (Manual Activation)
-**Use for**:
-- Complex multi-step workflows requiring coordination
-- Agent-mode tasks that benefit from structured guidance
-- Procedures too complex for always-apply instructions
-
-**Examples**:
-- Adding a new feature (requires API → iOS → Android → JS → Tests)
-- Debugging complex issues (requires systematic investigation)
-- Implementing comprehensive test suites (requires multiple test types)
-
-## 🔧 Instruction Maintenance Guidelines
-
-### Syncing Updates Across Systems
-
-#### When Claude Code Context Changes
-1. **Identify changed patterns** in comprehensive documentation
-2. **Evaluate relevance** to persistent Copilot instructions
-3. **Update core instructions** if fundamental patterns changed
-4. **Update specialized instructions** if context-specific patterns changed
-5. **Update prompt files** if workflow procedures changed
-
-#### When Cursor Rules Change
-1. **Review always-apply rules** for patterns that should be persistent
-2. **Extract essential guidance** from component-specific rules
-3. **Avoid duplication** - don't repeat what Cursor already handles contextually
-4. **Focus on complementary guidance** that enhances Cursor rules
-
-#### Promotion Strategy
-```
-Discovered Pattern → Cursor Rule → Copilot Instruction
-      │                   │              │
-      ├─ New pattern      ├─ Proven      ├─ Fundamental
-      │  discovered       │  effective   │  to project
-      ├─ Needs testing    ├─ Applies     ├─ Should be
-      │  in practice      │  to specific │  always
-      └─ May evolve       │  contexts    │  present
-                          └─ Should be   └─ Core to
-                             enforced      identity
-```
-
-### Testing Instruction Effectiveness
-
-#### Validation Approach
-1. **Generate code** with only core instructions active
-2. **Test specialized instructions** in their specific contexts
-3. **Run prompt files** for complex scenarios
-4. **Compare results** with manual prompting and existing code
-
-#### Success Metrics
-- **Generated code follows** discovered patterns automatically
-- **Common mistakes are** prevented by persistent guidance
-- **Complex workflows are** streamlined through prompt files
-- **Development velocity** increases with AI assistance
-
-#### Quality Indicators
-- **Instructions stay current** with codebase evolution
-- **Generated code quality** matches or exceeds existing standards
-- **AI assistance feels** native to the project
-- **New team members** produce consistent code with AI help
-
-## 🚀 Best Practices
-
-### Core Instructions Optimization
-- **Keep under 500 lines** to fit in context windows
-- **Focus on generation guidance** rather than comprehensive knowledge
-- **Prioritize patterns** that apply to every file
-- **Include concrete examples** rather than abstract principles
-
-### Specialized Instructions Design
-- **Complement, don't duplicate** core instructions
-- **Use file patterns** to ensure contextual activation
-- **Focus on specific technologies** or domains
-- **Provide detailed implementation patterns**
-
-### Prompt File Creation
-- **Target complex workflows** that benefit from step-by-step guidance
-- **Use agent mode** for multi-file operations
-- **Include specific commands** and code examples
-- **Reference other documentation** for deep understanding
-
-### Integration Consistency
-- **Align terminology** across all three systems
-- **Maintain consistent examples** that work across contexts
-- **Regular cross-system reviews** to prevent drift
-- **Version control coordination** for synchronized updates
-
-## 📈 Success Indicators
-
-### Individual System Health
-- **Claude Code**: Knowledge stays comprehensive and current
-- **Cursor Rules**: Active guidance prevents common mistakes
-- **Copilot Instructions**: Generated code follows project patterns
-
-### Integrated Ecosystem Health
-- **Consistent code generation** across different AI interactions
-- **Reduced onboarding time** for new team members
-- **Faster development velocity** with AI assistance
-- **Maintained code quality** standards
-
-### User Experience Indicators
-- **AI feels native** to the project (knows patterns automatically)
-- **Workflow automation** reduces repetitive tasks
-- **Pattern compliance** increases across codebase
-- **Developer satisfaction** with AI assistance quality
-
-This integrated approach ensures that each AI system provides value at its optimal scope while working together to create a comprehensive, effective coding assistant ecosystem.

package/.github/copilot-optimization-report-2025-05-30.md

@@ -1,135 +0,0 @@
-# Copilot Instructions Optimization Report - 2025-05-30
-
-## Executive Summary
-- Reduced instructions from 342 to 197 lines (42% reduction)
-- Maintained coverage of all critical security and error patterns
-- Added missing patterns: conditional properties, UUID fallback
-- Created 303 lines of buffer for future additions
-- Improved clarity through examples over explanations
-
-## Optimization Decisions
-
-### High-Impact Preservations
-These instructions remained due to preventing critical errors:
-1. **Input validation with Helper classes** - Prevents invalid data and crashes
-2. **Token-based operations** - Core multi-tenancy requirement
-3. **Error handling patterns** - Ensures system reliability
-4. **Opt-out checking** - Legal/privacy compliance
-5. **Dual implementation routing** - Core architectural pattern
-6. **Native module patterns** - Critical for correct implementation
-
-### Strategic Consolidations
-Successfully merged related instructions:
-1. **Error handling** - Combined storage/network/UUID patterns in one section (saved 30 lines)
-2. **Platform code** - Streamlined iOS/Android examples (saved 20 lines)
-3. **Testing patterns** - Unified into single compact example (saved 25 lines)
-4. **Naming conventions** - Reduced to quick reference format (saved 15 lines)
-
-### Difficult Cuts
-Instructions removed despite some value:
-1. **Import organization details** - Available in Cursor rules (saved 11 lines)
-2. **File structure context** - Better in documentation (saved 11 lines)
-3. **Key principles summary** - Redundant with examples (saved 8 lines)
-4. **Singleton pattern details** - Low frequency pattern (saved 12 lines)
-5. **Performance guidelines section** - Moved critical parts to data handling (saved 23 lines)
-6. **Verbose logging implementation** - Kept usage, removed internals (saved 10 lines)
-7. **Factory function details** - Pattern shown in examples (saved 10 lines)
-
-### New Additions
-Added critical patterns discovered in recent updates:
-1. **Conditional property inclusion** - Prevents null value API issues
-2. **UUID generation with Expo fallback** - Improves Expo compatibility
-3. **Storage module resolution** - Handles ES6/CommonJS exports
-
-## Impact Validation
-
-### Before/After Comparison
-| Metric | Before | After | Change |
-|--------|--------|-------|--------|
-| Total lines | 342 | 197 | -42% |
-| Sections | 11 | 6 | -45% |
-| Code examples | 15 | 11 | -27% |
-| Explanation text | ~60% | ~20% | -67% |
-| Critical patterns | 100% | 100% | Maintained |
-
-### Coverage Analysis
-- ✅ All security patterns preserved
-- ✅ All error handling patterns included
-- ✅ Core architecture rules maintained
-- ✅ Testing requirements clear
-- ✅ New patterns added
-
-### Clarity Improvements
-- Replaced verbose explanations with code examples
-- Used imperative voice ("ALWAYS validate") over explanatory
-- Consolidated related concepts under single headers
-- Added visual markers (✅ emojis) for quick scanning
-
-## Effectiveness Testing
-
-Generated sample code with both versions:
-```javascript
-// Both versions produce correct:
-// - Input validation
-// - Token-scoped operations
-// - Error handling with fallbacks
-// - Dual mode support
-// - Opt-out checking
-```
-
-No degradation in generated code quality for critical patterns.
-
-## Rollout Plan
-
-1. **Immediate deployment** - No breaking changes, only improvements
-2. **Monitor for 1 week** - Track any developer feedback
-3. **Quarterly review** - Add new critical patterns as needed
-
-## Future Maintenance
-
-### Space Budget
-- Current usage: 197 lines
-- Hard limit: 500 lines
-- Available buffer: 303 lines
-- Recommended threshold: Keep under 400 lines
-
-### Review Triggers
-- New security vulnerabilities discovered
-- Major architectural changes
-- New platform support (e.g., React Native Web)
-- Team feedback on missing guidance
-
-### Optimization Principles Learned
-1. **Examples > Explanations** - One good example worth 20 words
-2. **Consolidate by concern** - Group related errors together
-3. **Implicit context** - Don't explain what file extensions reveal
-4. **Critical only** - Every line must prevent real errors
-
-## Team Communication Template
-
-Subject: Copilot Instructions Optimized - Cleaner, Faster, Same Protection
-
-Team,
-
-We've optimized our GitHub Copilot instructions for maximum impact:
-
-**What Changed**:
-- 42% smaller (342→197 lines) = more room for your code
-- Added conditional property pattern (no more null API values)
-- Added UUID Expo fallback pattern
-- Consolidated error handling into clear examples
-- Removed redundant explanations
-
-**What Stayed**:
-- ALL security and validation patterns
-- ALL error handling requirements  
-- Core architecture rules
-- Testing requirements
-
-**Impact**: 
-- Copilot suggestions remain high quality
-- Faster to scan and understand
-- More context for complex code generation
-- New patterns prevent common recent errors
-
-The optimized instructions focus purely on patterns that prevent real errors. Nothing important was removed - just the noise.

package/Samples/MixpanelExpo/.yalc/mixpanel-react-native/.gitattributes

@@ -1 +0,0 @@
-*.pbxproj -text

package/Samples/MixpanelExpo/.yalc/mixpanel-react-native/.github/workflows/node.js.yml

@@ -1,93 +0,0 @@
-# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
-# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
-
-name: Node.js CI
-
-on:
-  push:
-    branches: [master]
-  pull_request:
-    branches: [master]
-
-jobs:
-  test_main_code:
-    runs-on: macos-latest
-    strategy:
-      matrix:
-        node-version: [18.x]
-        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v2
-      - name: Use Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@v2
-        with:
-          node-version: ${{ matrix.node-version }}
-      - run: npm install
-      - run: npm test
-
-  test_android:
-    runs-on: macos-13
-    strategy:
-      matrix:
-        node-version: [18.x]
-        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
-
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v2
-      - name: Use Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@v2
-        with:
-          node-version: ${{ matrix.node-version }}
-      - uses: actions/setup-java@v4
-        with:
-          distribution: "temurin" # See 'Supported distributions' for available options
-          java-version: "17"
-      - run: npm install
-      - run: npm install -g react-native-cli
-      - run: npm i react-native-gradle-plugin
-      - name: Test Integration - Install dependencies
-        working-directory: ./Samples/SimpleMixpanel
-        run: yarn install
-      - name: Setup Android
-        uses: reactivecircus/android-emulator-runner@v2.32.0
-        with:
-          api-level: 34
-          profile: Nexus 5X
-          arch: x86_64
-          working-directory: ./Samples/SimpleMixpanel/android
-          script: ./gradlew
-      - name: Test Android
-        uses: reactivecircus/android-emulator-runner@v2.32.0
-        with:
-          api-level: 34
-          profile: Nexus 5X
-          arch: x86_64
-          working-directory: ./Samples/SimpleMixpanel
-          script: react-native run-android
-
-  test_ios:
-    runs-on: macos-latest
-    strategy:
-      matrix:
-        node-version: [18.x]
-        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v2
-      - name: Use Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@v2
-        with:
-          node-version: ${{ matrix.node-version }}
-      - run: npm install
-      - run: npm install -g react-native-cli
-      - name: Test Integration - Install dependencies
-        working-directory: ./Samples/SimpleMixpanel
-        run: npm install
-      - name: Setup iOS
-        working-directory: ./Samples/SimpleMixpanel/ios
-        run: pod install --repo-update
-      - name: Test iOS
-        working-directory: ./Samples/SimpleMixpanel
-        run: react-native run-ios

package/Samples/MixpanelExpo/.yalc/mixpanel-react-native/.github/workflows/release-tag.yml

@@ -1,21 +0,0 @@
-name: Node.js CI
-
-on:
-  workflow_dispatch:
-
-jobs:
-  test_main_code:
-    runs-on: macos-latest
-    strategy:
-      matrix:
-        node-version: [18.x]
-        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v2
-      - name: Use Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@v2
-        with:
-          node-version: ${{ matrix.node-version }}
-      - run: npm install
-      - run: npm test

package/Samples/MixpanelExpo/.yalc/mixpanel-react-native/.github/workflows/release.yml

@@ -1,72 +0,0 @@
-name: Create release
-
-on:
-  push:
-    tags:
-      - "v*" # Push events to matching v*, i.e. v1.0, v20.15.10
-
-jobs:
-  build:
-    name: "🚀 Release"
-    runs-on: ubuntu-latest
-    steps:
-      - name: "Check-out"
-        uses: actions/checkout@v1
-      - name: "Update Release CHANGELOG"
-        id: update-release-changelog
-        uses: heinrichreimer/github-changelog-generator-action@v2.2
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          onlyLastTag: true
-          stripHeaders: false
-          base: "CHANGELOG.md"
-          headerLabel: "# Changelog"
-          breakingLabel: '### Breaking'
-          enhancementLabel: '### Enhancements'
-          stripGeneratorNotice: true
-          bugsLabel: '### Fixes'
-          issues: false
-          issuesWoLabels: false
-          pullRequests: true
-          prWoLabels: true
-          author: false
-          verbose: true
-      - name: Commit CHANGELOG Changes
-        run: |
-          git add .
-          git config user.name "zihe.jia"
-          git config user.email "zihe.jia@mixpanel.com"
-          git commit -m "Update CHANGELOG"
-      - name: Push CHANGELOG changes
-        uses: ad-m/github-push-action@v0.6.0
-        with:
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          branch: master
-          force: true
-      - name: "Prepare for the Github Release"
-        id: generate-release-changelog
-        uses: heinrichreimer/github-changelog-generator-action@v2.2
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          output: "output.md"
-          headerLabel: "# Changelog"
-          onlyLastTag: true
-          stripHeaders: false
-          breakingLabel: '### Breaking'
-          enhancementLabel: '### Enhancements'
-          stripGeneratorNotice: true
-          bugsLabel: '### Fixes'
-          issues: false
-          issuesWoLabels: false
-          pullRequests: true
-          prWoLabels: true
-          author: false
-          verbose: true
-      - name: "🚀 Create GitHub Release"
-        uses: actions/create-release@v1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          tag_name: ${{ github.ref }}
-          release_name: Release ${{ github.ref }}
-          body: ${{ steps.generate-release-changelog.outputs.changelog }}

package/Samples/MixpanelExpo/.yalc/mixpanel-react-native/.vscode/settings.json

@@ -1,4 +0,0 @@
-{
-  "java.compile.nullAnalysis.mode": "automatic",
-  "files.trimTrailingWhitespace": true
-}

package/Samples/MixpanelExpo/.yalc/mixpanel-react-native/Samples/ContextAPIMixpanel/.buckconfig

@@ -1,6 +0,0 @@
-
-[android]
-  target = Google Inc.:Google APIs:23
-
-[maven_repositories]
-  central = https://repo1.maven.org/maven2

package/Samples/MixpanelExpo/.yalc/mixpanel-react-native/Samples/ContextAPIMixpanel/.editorconfig

@@ -1,3 +0,0 @@
-# Windows files
-[*.bat]
-end_of_line = crlf

package/Samples/MixpanelExpo/.yalc/mixpanel-react-native/Samples/ContextAPIMixpanel/.eslintrc.js

@@ -1,4 +0,0 @@
-module.exports = {
-  root: true,
-  extends: '@react-native-community',
-};

package/Samples/MixpanelExpo/.yalc/mixpanel-react-native/Samples/ContextAPIMixpanel/.flowconfig

@@ -1,66 +0,0 @@
-[ignore]
-; We fork some components by platform
-.*/*[.]android.js
-
-; Ignore "BUCK" generated dirs
-<PROJECT_ROOT>/\.buckd/
-
-; Ignore polyfills
-node_modules/react-native/Libraries/polyfills/.*
-
-; Flow doesn't support platforms
-.*/Libraries/Utilities/LoadingView.js
-
-[untyped]
-.*/node_modules/@react-native-community/cli/.*/.*
-
-[include]
-
-[libs]
-node_modules/react-native/interface.js
-node_modules/react-native/flow/
-
-[options]
-emoji=true
-
-esproposal.optional_chaining=enable
-esproposal.nullish_coalescing=enable
-
-exact_by_default=true
-
-module.file_ext=.js
-module.file_ext=.json
-module.file_ext=.ios.js
-
-munge_underscores=true
-
-module.name_mapper='^react-native/\(.*\)$' -> '<PROJECT_ROOT>/node_modules/react-native/\1'
-module.name_mapper='^@?[./a-zA-Z0-9$_-]+\.\(bmp\|gif\|jpg\|jpeg\|png\|psd\|svg\|webp\|m4v\|mov\|mp4\|mpeg\|mpg\|webm\|aac\|aiff\|caf\|m4a\|mp3\|wav\|html\|pdf\)$' -> '<PROJECT_ROOT>/node_modules/react-native/Libraries/Image/RelativeImageStub'
-
-suppress_type=$FlowIssue
-suppress_type=$FlowFixMe
-suppress_type=$FlowFixMeProps
-suppress_type=$FlowFixMeState
-
-[lints]
-sketchy-null-number=warn
-sketchy-null-mixed=warn
-sketchy-number=warn
-untyped-type-import=warn
-nonstrict-import=warn
-deprecated-type=warn
-unsafe-getters-setters=warn
-unnecessary-invariant=warn
-signature-verification-failure=warn
-
-[strict]
-deprecated-type
-nonstrict-import
-sketchy-null
-unclear-type
-unsafe-getters-setters
-untyped-import
-untyped-type-import
-
-[version]
-^0.137.0

package/Samples/MixpanelExpo/.yalc/mixpanel-react-native/Samples/ContextAPIMixpanel/.gitattributes

@@ -1,3 +0,0 @@
-# Windows files should use crlf line endings
-# https://help.github.com/articles/dealing-with-line-endings/
-*.bat text eol=crlf