Packages

@flue/vite

2.3.1 · 18 Nov 2026Apache-2.0343k / weekRepositoryHomepagenpmAtom feed

Upgrading @flue/vite From 2.0.1 to 2.3.1

14 releases in betweenevery note read

  1. 2.0.1yours
  2. 13 releases
  3. 2.3.1target
  4. 4 pre
0
changes to make
0
advisories fixed
2
new
19
fixes

Release by release

  1. 2.3.1

    18 Nov 20262 fixes
    • Fixed

      Updated @earendil-works/pi-ai and @earendil-works/pi-agent-core to 1.5.2, fixing builds that picked up pi-ai 1.5. @flue/runtime 2.3.0 imported TypeBox through @earendil-works/pi-ai, which stopped re-exporting it in 1.5.0, so a fresh install failed vite build. Flue now depends on typebox directly and requires pi ^1.5.0; remove any overrides that held pi at 1.4. If your own code imports Type or Static from @earendil-works/pi-ai, import them from typebox instead. Pi now validates tool arguments with its own JSON Schema validator, which coerces a little more (for example "3" for a number) and words its validation errors differently. OpenAI-compatible requests with no tools no longer send "tools":; set compat.requiresToolsWithToolHistory: true on models behind proxies that require it, such as older LiteLLM versions in front of Anthropic.

    • Fixed

      Workers AI binding models on the Responses API declare tools the way pi's own OpenAI provider does. Since pi 1.4, the binding passed a boolean where pi expected a tool-support mode, so a model without deferred tool loading could leave tools added mid-conversation out of its request. Models that support mid-conversation tool additions now declare every tool through additional_tools input items.

  2. 2.3.0

    12 Oct 20261 new · 6 fixes
    • New

      Updated @earendil-works/pi-ai and @earendil-works/pi-agent-core to 1.1.0. New models resolve with no configuration, including Claude Sonnet 5.5 (anthropic/claude-sonnet-5-5), Claude Haiku 5.5 (anthropic/claude-haiku-5-5), and GPT-6.1 Sol (openai/gpt-6.1-sol). Azure users must update: Pi renamed the Azure provider from azure-openai-responses to azure, so change azure-openai-responses/... model specifiers and providers config entries to azure. The AZURE_OPENAI_* environment variables are unchanged. Tool and turn durationMs values now come from Pi's monotonic timing, so a tool's duration covers only its execution, not Flue's hooks or result storage.

    • Fixed

      useAgentFinish callbacks once again see state written during the response. Since 2.2.0, finish hooks ran against the agent render from before the response's final turn, so a durable guard set by a finish callback — the documented usePersistentState pattern for appending a reminder once — was never observed: the callback re-appended on every cycle until the response failed at the runaway-loop ceiling. The agent now re-renders before each finish-hook cycle (#818).

    • Fixed

      read_skill_resource accepts a packaged skill path without its leading /. Models often echo the advertised /.flue/packaged-skills/... path without the slash, and the read failed as not found (#781).

    • Fixed

      The local sandbox SIGKILLs a command's whole process group after the grace period, even when the shell exits first. On an exec() timeout or abort, the pending SIGKILL was cancelled once the shell's pipes closed, so a process that ignored SIGTERM and held none of the shell's output kept running after exec() returned (#809).

    • Fixed

      Execution interceptors see agentName on model, tool, and shell steps, not only on the outer agent operation. The root harness's execution context carried only the instance id, so an interceptor that branches per agent took its default branch on every step (#785).

    • Fixed

      flue init --target cloudflare scaffolds the Workers AI binding that keyless cloudflare/... models need, commented out in wrangler.jsonc. The generated agent suggested switching to a keyless Cloudflare model but nothing declared env.AI; it now points at the binding to uncomment. The binding stays off by default because it reaches your Cloudflare account even in local dev (#739).

    • Fixed

      The E2B sandbox blueprint returns a non-zero exit from exec() instead of throwing. E2B's commands.run() throws CommandExitError on a non-zero exit, so a failing command rejected with no command or stderr instead of resolving with its exitCode. The blueprint is bumped to version 2; run flue update sandbox e2b to update an existing integration (#805).

  3. 2.2.1 – 2.2.22 releases, nothing new or fixed in the notes

  4. 2.2.0

    28 Sep 20261 fix
    • Fixed

      Markdown and skill imports written as Node subpath imports (package.json imports, e.g. import core from '#src/prompts/core.md') now transform like relative and package specifiers in both dev and production builds: .md imports load as markdown text and SKILL.md imports package the skill directory. Previously the leading # was mistaken for a fragment marker, the import was left untransformed, and Vite tried to parse the Markdown file as JavaScript. Queried forms (?raw, ?url, ...) continue to be delegated to Vite.

  5. 2.1.1

    23 Sep 20261 new
    • New

      Allow Flue packages and newly scaffolded applications to share a compatible Hono installation. Hono dependencies now use ^4.12.32, preventing fresh projects from installing a newer root Hono alongside the runtime's older exact version and failing typecheck.

  6. 2.0.8 – 2.1.02 releases, nothing new or fixed in the notes

  7. 2.0.7

    15 Sep 20261 fix
    • Fixed

      Markdown importers written in JSX (.tsx/.jsx) are now scanned correctly. SKILL.md imports that belong to the Agents SDK's virtual skill registry are left to its owning plugin instead of being claimed by Flue's transform.

  8. 2.0.6

    14 Sep 20261 fix
    • Fixed

      Published packages once again include the bundled Flue documentation. The 2.0.4 and 2.0.5 releases omitted the generated docs/ directories from @flue/cli, @flue/runtime, and @flue/sdk, causing commands such as flue docs read guide/sandboxes to fail.

7 internal lines (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.