Skip to content

Update dependency teddy to v1.2.1 - #301

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/teddy-1.x
Open

Update dependency teddy to v1.2.1#301
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/teddy-1.x

Conversation

@renovate

@renovate renovate Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
teddy (source) 1.1.41.2.1 age confidence

Release Notes

rooseveltframework/teddy (teddy)

v1.2.1

Compare Source

  • Fixed <include> tags inside a <loop> so that the included partial's <if>, <unless>, one line conditionals, and nested <loop> tags can read the loop's key and val. Previously the partial's contents were parsed against the model as it stood outside the loop, so a partial could print the loop's val through a {variable} but any tag that branched on it behaved as though it were not there. Includes are now expanded by the loop, once per iteration, against that iteration's model, which is how partials behave in other templating engines.
  • Updated dependencies.

v1.2.0

Compare Source

  • Breaking: Disabled template caching for templates read from the filesystem by default. Teddy used to keep every template it read and never read it again, so editing a template had no effect until the process restarted or teddy.clearTemplates() was called. Caching is now off by default, which is how most other templating engines (e.g. ejs or pug) treat their own caching, so a template that changes on disk is picked up on the next render.
    • If you use Teddy as an Express view engine you do not need to do anything: Express supplies its own view cache setting, which it enables in production and disables in development, and Teddy now uses it. That means production keeps caching and development stops needing a restart.
    • Templates registered with teddy.setTemplate are unaffected. Those are always kept, since registering one by hand is the only way to supply a template in the browser.
    • To get the old behavior back, call teddy.setCacheTemplates(true) when instantiating Teddy, or pass cache: true in the model on each render.
  • Added teddy.setCacheTemplates(boolean) to control the above, and support for a cache option in the model, which takes precedence over both that setter and Express's view cache.
  • Altered teddy.clearTemplates() to now clear the templates that were read from the filesystem, not just the ones registered by hand.
  • Fixed <include> resolving its partial through the template registry rather than through the loader, which meant an included template could not be re-read after it changed.
  • Fixed one line conditionals so that a sequence of them on the same element is evaluated in full, rather than all but one being discarded. <p if-a true='class="x"' if-b true='data-y="z"'> now applies both outcomes.
  • Improved performance considerably in several places.
  • Made various improvements to the automated test suite.
  • Updated dependencies.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot changed the title Update dependency teddy to v1.2.0 Update dependency teddy to v1.2.1 Aug 27, 2026
@renovate
renovate Bot force-pushed the renovate/teddy-1.x branch from eee0771 to 572195c Compare August 27, 2026 21:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants