-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat(tracing): Expose BrowserTracing
in non-tracing bundles
#7479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
rollup/plugins/bundlePlugins.js
Outdated
@@ -194,11 +194,15 @@ export function makeExcludeBlockPlugin(type) { | |||
); | |||
|
|||
const browserIndexFilePath = path.resolve(__dirname, '../../packages/browser/src/index.ts'); | |||
const browserIntegrationsIndexFilePath = path.resolve(__dirname, '../../packages/browser/src/integrations/index.ts'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
l: Would you mind updating the JSDoc of this function? I think it's pretty outdated by now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually got rid of this now!
In order to avoid breaking the bundler when a user opts out of tracing there.
ccc1043
to
f71eb69
Compare
So I updated this to make this work properly. |
size-limit report 📦
|
f71eb69
to
538ae59
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, the separate index files look like the cleaner option now!
In order to avoid breaking the bundler when a user opts out of tracing there.