Author a draft `Package.swift` for RNSentry

Open
#6,173 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
react-native, swift, typescript
Domain
build-system, mobile

Research direction

Start with the linked React Native SPM autolinking proposal and the repository's existing iOS dependency layout, then author the draft Package.swift. Done means the manifest is present and integration issues are surfaced; end-to-end consumption is not required until non-experimental autolinking exists.

Written by the indexing model from the issue text.

Description

Feature React-Native

RNSentry does not currently publish a Package.swift. To support React Native's eventual SPM-based autolinking (tracked broadly in https://github.com/react-native-community/discussions-and-proposals/issues/587) and Apple's preferred distribution model, we need a Swift Package manifest that consumers can resolve.

This issue produces a draft manifest. It is not expected to be end-to-end consumable until React Native's community CLI ships non-experimental SPM autolinking. The goal is to be ready, and to surface integration issues early.

Dominant language
TypeScript
Stars
1.8k
Forks
367
Avg merge
1d 6h
Merged PRs (30d)
94

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-react-native

All issues in getsentry/sentry-react-native

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.