fix: align package exports with documentation across the SDK#11
Merged
Conversation
Audited every package's public exports against the docs (logtide.dev) and fixed all import/usage mismatches found. - @logtide/browser: export LogtideErrorBoundary (React error boundary) as documented for React users; react is an optional peer dependency. @logtide/nextjs/client now re-exports this shared implementation. - @logtide/nuxt: implement the documented useLogtide() auto-imported composable; honor tracesSampleRate and support apiUrl/apiKey config (the module previously dropped them and required a dsn). - @logtide/cli: accept the documented `--path` option and `--apiKey`/`--apiUrl` aliases for `sourcemaps upload`. - @logtide/sdk-node README: import middleware from the /middleware subpath. - @logtide/nuxt README: correct the default service value to 'nuxt'. Bump all packages to 0.11.0.
This was referenced Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #10. After another "no exported member" report (
LogtideErrorBoundary), I audited every package's public exports against the documentation (logtide.dev + READMEs) — one agent per package — and fixed every code-side import/usage mismatch found.Fixes (code-side)
@logtide/browser— exportLogtideErrorBoundary(the React error boundary documented for React users at logtide.dev/integrations/react).reactis now an optional peer dependency.@logtide/nextjs/clientre-exports this single shared implementation instead of keeping its own copy.@logtide/nuxt— implement the documenteduseLogtide()auto-imported composable; honortracesSampleRate; supportapiUrl+apiKeyconfig (the module previously dropped them and bailed unless adsnwas set).@logtide/cli— accept the documented--pathoption and--apiKey/--apiUrlaliases forsourcemaps upload(directory can be positional or--path).@logtide/sdk-nodeREADME — import middleware from the/middlewaresubpath (wherelogTideMiddleware/logTideFastifyPluginactually live).@logtide/nuxtREADME — correct documented defaultserviceto'nuxt'.Audit result for the other packages
nextjs,sveltekit,angular,express,fastify,hono,elysia,core,types— exports clean, every documented import resolves. Remaining issues there are docs-site-only inaccuracies (separate repo) and are listed for the docs team, not fixed here.Tests (TDD)
New tests:
browser/tests/error-boundary.test.ts,cli/tests/cli.test.ts,nuxt/tests/composables.test.ts.Full monorepo green: build + typecheck + all package test suites pass (browser 49, core 121, node 23, fastify 31, express 28, nextjs 17, sveltekit 20, nuxt 11, cli 15, angular 7, hono 14, elysia 11).
All packages bumped
0.10.0 → 0.11.0.