add Expo config plugin

[kbrandwijk]

📢 Type of change

• Bugfix
• New feature
• Enhancement
• Refactoring

📜 Description

This PR adds the Expo config plugin that used to be part of the sentry-expo package.
The plugin implementation is identical, except for moving the configuration properties over from the (deprecated) postPublish configuration in app.json to config plugin properties that is the default for config plugins.

💡 Motivation and Context

Closes #3263
For more details, see the linked issue and the parent issue.

💚 How did you test it?

Tested by building and testing the config plugin locally, and adding it to a local Expo test project to see if the config plugin was applied successfully.

📝 Checklist

• I reviewed submitted code
• I added tests to verify changes
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
• All tests passing
• No breaking changes

🔮 Next steps

[krystofwoldrich]

@kbrandwijk Thank you, this is a good start. There are a few minor things we'll need to adjust.

I've changed the target to expo branch so we can get all changes there before merging to main and releasing.

I would also like to add a simple Expo app to test a build with the plugin in CI. But we can do that in another PR.

[krystofwoldrich]

We can move the test to /test/expo-plugin/* and change the naming from -test.ts to .test.ts.

We keep all tests in /test.

[krystofwoldrich]

@kbrandwijk So with this PR the configuration of the plugin would look like this:

app.config.js

const { withSentry } = require('@sentry/react-native/plugin/build/withSentry');

const config = {
	name: 'my app',
};

module.exports = withSentry(config, {
	url: 'https://example.sentry.url/',
	authToken: 'example-token',
	project: 'project-slug',
	organization: 'org-slug',
});

OR in JSON

{
	"name": "my app",
	"plugins": [
		[
			"@sentry/react-native/plugin/build/withSentry",
			{
				"url": "https://example.sentry.url/",
				"authToken": "example-token",
				"project": "project-slug",
				"organization": "org-slug"
			}
		]
	]
}

[krystofwoldrich]

To keep the PR small and easy to understand I created some follow-up tasks.

• Create @sentry/react-native/expo for simple plugin import #3393
• Update Expo Plugin to use Sentry Xcode shell scripts #3394

[kbrandwijk]

@kbrandwijk So with this PR the configuration of the plugin would look like this:

app.config.js

const { withSentry } = require('@sentry/react-native/plugin/build/withSentry');

const config = {
	name: 'my app',
};

module.exports = withSentry(config, {
	url: 'https://example.sentry.url/',
	authToken: 'example-token',
	project: 'project-slug',
	organization: 'org-slug',
});

OR in JSON

{
	"name": "my app",
	"plugins": [
		[
			"@sentry/react-native/plugin/build/withSentry",
			{
				"url": "https://example.sentry.url/",
				"authToken": "example-token",
				"project": "project-slug",
				"organization": "org-slug"
			}
		]
	]
}

Correct

[kbrandwijk]

Thank you for the PR feedback. After applying the lint suggestion, I addressed most of the issues, but was left with a few nasty ones that probably require a bit more work to fix (around the xcode types for example). I disabled those for now, I suggest we circle back to these in a follow up ticket.

[krystofwoldrich]

@kbrandwijk Sounds good. Thank you.

[kbrandwijk]

@kbrandwijk So with this PR the configuration of the plugin would look like this:
app.config.js

const { withSentry } = require('@sentry/react-native/plugin/build/withSentry');

const config = {
	name: 'my app',
};

module.exports = withSentry(config, {
	url: 'https://example.sentry.url/',
	authToken: 'example-token',
	project: 'project-slug',
	organization: 'org-slug',
});

OR in JSON

{
	"name": "my app",
	"plugins": [
		[
			"@sentry/react-native/plugin/build/withSentry",
			{
				"url": "https://example.sentry.url/",
				"authToken": "example-token",
				"project": "project-slug",
				"organization": "org-slug"
			}
		]
	]
}

Correct

Actually, for end user purposes, it would just be:

{
	"name": "my app",
	"plugins": [
		[
			"@sentry/react-native",
			{
				"url": "https://example.sentry.url/",
				"authToken": "example-token",
				"project": "project-slug",
				"organization": "org-slug"
			}
		]
	]
}

[krystofwoldrich]

Thank you. Looks good. 👍

[brentvatne]

it looks like we left some sentry-expo references in here, should update to this lib name

[brentvatne]

we should replace this url with https://github.com/getsentry/sentry-react-native

[objectiveSee]

Any update on when this release will be stable? We are setting up Sentry for our app that uses Expo 49 and I am having issues with source maps when using Expo's sentry library. If this alpha is almost ready then we might just wait to use this instead.

[krystofwoldrich]

@objectiveSee We are planning two releases before the stable, which should come in the upcoming weeks.