Skip to content

Commit 1f3a796

Browse files
authored
docs: Add docs on building the SDK (#10368)
As this comes up every now and then (e.g. #5108), I gather it makes sense to document how to build the SDK youself. I added a note to explicitly state that there are no guarantees there.
1 parent 71a84ab commit 1f3a796

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

CONTRIBUTING.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,11 @@ able to use it. From the top level of the repo, there are three commands availab
3737
dependencies (`utils`, `core`, `browser`, etc), and all packages which depend on it (currently `gatsby` and `nextjs`))
3838
- `yarn build:dev:watch`, which runs `yarn build:dev` in watch mode (recommended)
3939

40+
You can also run a production build via `yarn build`, which will build everything except for the tarballs for publishing to NPM.
41+
You can use this if you want to bundle Sentry yourself. The build output can be found in the packages `build/` folder, e.g. `packages/browser/build`.
42+
Bundled files can be found in `packages/browser/build/bundles`.
43+
Note that there are no guarantees about the produced file names etc., so make sure to double check which files are generated after upgrading.
44+
4045
## Testing SDK Packages Locally
4146

4247
To test local versions of SDK packages, for instance in test projects, you have a couple of options:

0 commit comments

Comments
 (0)