10 KiB
@assistant-ui/next
0.0.10
Patch Changes
0.0.9
Patch Changes
- Updated dependencies [
d162f44]:- @assistant-ui/x-generative-compiler@0.0.7
0.0.8
Patch Changes
-
Updated dependencies [
cefcf27,32f1b05,0c51b90,048e20c,056eea8]:- @assistant-ui/x-generative-compiler@0.0.6
0.0.7
Patch Changes
-
Updated dependencies [
bb38d08]:- @assistant-ui/x-generative-compiler@0.0.5
0.0.6
Patch Changes
- #4327
1437805- fix: give each"use generative"module a distinct bundler-redirect identity so two toolkits in one app no longer collide undernext dev(@AVGVSTVS96)
0.0.5
Patch Changes
-
#4266
906fae9- docs: referenceAISDKToolkitinstead of the deprecatedgenerativeToolsin the README (@Yonom) -
#4256
44ff4bf- feat: rename hitlTool to humanTool while keeping deprecated compatibility aliases (@Yonom) -
Updated dependencies [
a0a0769,ca191dc,40813e6,7d2b2b7,15878d8,44ff4bf,451c191]:- @assistant-ui/x-generative-compiler@0.0.4
0.0.4
Patch Changes
-
#4178
70de5eb- fix: resolve type-check errors —@assistant-ui/nextnow extends the Node tsconfig sonode:pathresolves, and drop an unused import inreact-langgraph(@Yonom) -
#4199
d9b3119- feat: the"use generative"compiler now understands generative-UI libraries. It splits everydefineGenerativeComponents({ ... })call (dropping each component'srenderand its client-only imports from the server build, keepingpropertieson both), unwraps the marker likedefineToolkit, and processes multipledefineToolkit/defineGenerativeComponentscalls anywhere in the module. A toolkit entry that is a method call on anew JSONGenerativeUI(...)instance (e.g.generative.present()) now passes through untouched — the library routes its halves via export conditions — while any other non-inline tool is still rejected. (@Yonom) -
#4200
4853543- fix(next): bust the"use generative"loader cache when the compiler changes.withAuinow folds a token derived from@assistant-ui/x-generative-compiler's version and dist mtime into the loader options, which Turbopack and webpack include in their transform cache key. Previously a change to the compiler (a published upgrade, or an in-place rebuild in a monorepo) could leave stale compiled"use generative"modules cached until.nextwas cleared. (@Yonom) -
Updated dependencies [
d9b3119,58f80e0,78ff336,5fe118d,dcd5897,69540af,ae54c55]:- @assistant-ui/x-generative-compiler@0.0.3
0.0.3
Patch Changes
-
#4176
27ae936- feat: add @assistant-ui/next — thewithAui()Next.js config wrapper and the compiler for the"use generative"directive that colocates a tool's schema, server-onlyexecute, and client-onlyrenderin one file (@Yonom) -
#4176
27ae936- feat: extract the framework-agnostic"use generative"compiler into the internal@assistant-ui/x-generative-compilerpackage.@assistant-ui/nextnow consumes the shared compiler instead of bundling its own copy, so other build integrations can reuse it. (@Yonom) -
#4176
27ae936- feat: move thedefineToolkitandhitluse-generative markers from@assistant-ui/nextinto@assistant-ui/core/react, so they ship once from every distribution (@assistant-ui/react,@assistant-ui/react-native,@assistant-ui/react-ink) and stay portable across build targets. Import them from@assistant-ui/reactinstead of@assistant-ui/next; they remain no-op markers stripped at build time by a"use generative"compiler. (@Yonom) -
Updated dependencies [
27ae936]:- @assistant-ui/x-generative-compiler@0.0.2
0.0.2
Patch Changes
-
#4172
1315789- feat: add @assistant-ui/next — thewithAui()Next.js config wrapper, thedefineToolkit()authoring helper, and the compiler for the"use generative"directive that colocates a tool's schema, server-onlyexecute, and client-onlyrenderin one file (@Yonom) -
Updated dependencies [
1315789,299d448,4429aa3,e76611f,76f7d16,eef724e,2dec3ae,fcb6baf]:- @assistant-ui/core@0.2.8