docs: publish .nojekyll so GitHub Pages serves underscore API pages (#952)

EOF

Co-authored-by: Cursor <[email protected]>

.all-contributorsrc

@@ -838,6 +838,33 @@
       "contributions": [
         "code"
       ]
+    },
+    {
+      "login": "spokodev",
+      "name": "spokodev",
+      "avatar_url": "https://avatars.githubusercontent.com/u/239690017?v=4",
+      "profile": "https://github.com/spokodev",
+      "contributions": [
+        "code"
+      ]
+    },
+    {
+      "login": "YacovGold",
+      "name": "YacovGold",
+      "avatar_url": "https://avatars.githubusercontent.com/u/8984042?v=4",
+      "profile": "https://github.com/YacovGold",
+      "contributions": [
+        "code"
+      ]
+    },
+    {
+      "login": "sarathfrancis90",
+      "name": "Sarath Francis",
+      "avatar_url": "https://avatars.githubusercontent.com/u/9289498?v=4",
+      "profile": "https://github.com/sarathfrancis90",
+      "contributions": [
+        "code"
+      ]
     }
   ],
   "contributorsPerLine": 7,

.cursor/rules/architecture.mdc

@@ -1,17 +0,0 @@
----
-description: Architecture overview for liquidjs internals
-alwaysApply: true
----
-
-## Async/sync duality via generators
-
-All core logic is written once as a `Generator` function (`function *`). Use `yield` where you'd normally `await` a potentially async value.
-
-- `toPromise(generator)` drives it **asynchronously** — awaits yielded promises.
-- `toValueSync(generator)` drives it **synchronously** — passes yielded values through as-is.
-
-Never duplicate logic into separate async and sync methods. A single generator serves both paths.
-
-When wrapping an async+sync function pair (e.g. `contains`/`containsSync`, `exists`/`existsSync`, `readFile`/`readFileSync`), use `toLiquidAsync(asyncFn, syncFn?)` which returns a `LiquidAsync<F>` — one function that picks the sync or async implementation based on a leading `sync: boolean` arg. Then `yield` the result inside a generator to let the driver handle it in both modes.
-
-See `src/util/async.ts`.

.cursor/rules/conventions.mdc

@@ -1,6 +0,0 @@
----
-description: Project conventions for liquidjs
-alwaysApply: true
----
-
-- Keep edits minimal: change only what the task requires, match existing style.

.cursor/rules/testing.mdc

@@ -1,17 +0,0 @@
----
-description: Testing conventions — e2e uses built dist, integration uses src
-globs: test/**/*.ts
-alwaysApply: false
----
-
-# Testing
-
-## End-to-end tests (`test/e2e`)
-
-- **Use the built package**, not TypeScript sources under `src/`.
-- Import the public API from the package root (for example `import { Liquid } from '../..'`), which resolves through `package.json` to **`dist/`** (`main`, `module`, etc.).
-- **Avoid** `import … from '../../src/liquid'` (or other `src/` paths) in `test/e2e/**` so e2e matches what consumers get from npm and you do not depend on an unbuilt tree.
-
-## Integration and unit tests
-
-- Tests under `test/integration/`, `src/**/*.spec.ts`, and similar may import from **`src/`** when the suite is meant to run against the current TypeScript sources (typical for this repo’s Jest setup).

.gitignore

@@ -11,9 +11,11 @@ coverage/
 node_modules/
 
 # tmp
-docs/public/js/liquid.browser.min.js
+.local/
+docs/themes/navy/source/js/liquid.browser.min.js
 docs/themes/navy/layout/partial/all-contributors.swig
 docs/themes/navy/layout/partial/financial-contributors.swig
+docs/themes/navy/layout/partial/used-by.swig
 dist/
 demo/*/yarn.json
 

AGENTS.md

@@ -0,0 +1,94 @@
+# LiquidJS
+
+A simple, expressive, extensible Liquid template engine for JavaScript — Shopify, Jekyll and GitHub Pages compatible, for Node.js, browsers, and the CLI, with TypeScript support. TypeScript in `src/`, bundles in `dist/`. Docs site in `docs/` (Hexo, `navy` theme).
+
+## Layout
+
+| Path | Contents |
+| --- | --- |
+| `src/parser`, `src/render`, `src/tags`, `src/filters` | Template parse and render |
+| `src/context`, `src/template`, `src/tokens` | Scope, templates, token stream |
+| `src/util/async.ts` | `toPromise`, `toValueSync`, `toLiquidAsync` |
+| `test/` | Jest |
+| `docs/source/` | Doc markdown; sidebar in `docs/source/_data/sidebar.yml` |
+| `docs/themes/navy/` | Layout, CSS, JS |
+| `.local/` | Scratch, repro, PoC (gitignored) |
+
+## Commands
+
+```
+npm run build          # after src/ changes, before npm test
+npm test
+npm run lint
+npm run check          # build + build:docs + test + lint + perf:diff (manual)
+npm run build:docs
+cd docs && npm start   # http://localhost:4000
+npm run perf:diff
+```
+
+PR CI (`pull_request`): build, lint, test, coverage, performance. Docs build runs on push to `master` only.
+
+PR titles: conventional format (`feat:`, `fix:`, `docs:`, …) — checked by CI. Releases on `master` use semantic-release from merged commits.
+
+Backward-compatible API changes expected unless doing an intentional major break.
+
+## Architecture
+
+All core logic is one `function *` per feature. Use `yield` where you'd normally `await` a potentially async value.
+
+- `toPromise(generator)` — async driver; awaits yielded promises
+- `toValueSync(generator)` — sync driver; passes yielded values through as-is
+
+Never duplicate logic into separate async and sync methods. One generator serves both paths.
+
+When wrapping an async+sync pair (e.g. `contains`/`containsSync`, `readFile`/`readFileSync`), use `toLiquidAsync(asyncFn, syncFn?)` — returns a `LiquidAsync<F>` that picks sync or async via a leading `sync: boolean` arg. `yield` the result inside a generator. See `src/util/async.ts`.
+
+## Style
+
+Make minimal changes only. Avoid sweeping edits. Always check after you made changes.
+
+- Change only what the task requires. No drive-by refactors, test harnesses, or extra files unless asked.
+- Match existing patterns in the file you edit.
+- Repro, PoC, and scratch files go in `.local/` — not tracked `poc/` folders or one-off scripts under `docs/`.
+
+### Comments
+
+- Do not add narrative comments. Code should be clear from structure and naming; if it needs explanation, refactor instead.
+- Comments follow existing repo usage only: non-obvious invariants, `@deprecated`, JSDoc on public API where TypeDoc needs it. Not for explaining changes to the author, migration history, or restating what the code already says.
+- Comments document the code; they do not fix unclear code.
+
+### Tests
+
+- Assert observable behavior, not internal implementation details.
+- Avoid duplicate coverage; keep test diffs minimal.
+- **E2E** (`test/e2e/`): import from the package root (resolves to `dist/` via `package.json`). Do not import from `src/` — e2e must match what npm consumers get.
+- **Integration/unit** (`test/integration/`, etc.): may import from `src/` against current TypeScript sources.
+
+### Docs site
+
+- Reuse existing asset paths under `docs/source/` and `docs/themes/navy/` — no new asset directories unless asked.
+- Front matter `title:` is plain text (no backticks).
+- `docs/source/llms.txt` — deployed to https://liquidjs.com/llms.txt for web agents (llms.txt spec).
+- After theme/markdown changes: build or serve locally, check in a browser (light and dark), not only curl or editor preview.
+
+### README
+
+- Research original sources before reordering contributors, logos, or lists.
+
+## Verify
+
+- Do not commit, push, amend, or open a PR unless asked.
+- After changes: verify yourself via CLI or UI (tests, `cd docs && npm start`, browser) before reporting done. Do not tell the user to check instead.
+- Before push on sweeping changes: run `npm run check`.
+- Confirm facts from `.github/workflows`, `package.json`, and library docs — not stale human docs or assumptions.
+- When replacing or integrating a library: read its docs and understand what the previous setup did before changing behavior.
+
+### Security fixes
+
+- Reproduce on current `master` first. Smallest fix that addresses the reported issue.
+- If Shopify/Ruby Liquid behaves the same, document unsafe usage in filter/docs instead of changing behavior.
+
+## Docs
+
+- Published: https://liquidjs.com
+- Repo agent instructions: this file (`AGENTS.md`)

CHANGELOG.md

@@ -1,3 +1,72 @@
+# [10.29.0](https://github.com/harttle/liquidjs/compare/v10.28.0...v10.29.0) (2026-08-11)
+
+
+### Features
+
+* add unregisterFilter method ([#946](https://github.com/harttle/liquidjs/issues/946)) ([69b2c58](https://github.com/harttle/liquidjs/commit/69b2c589f9b69a34427cb8533ddb938bd997914f))
+* **filters:** add squish filter ([#943](https://github.com/harttle/liquidjs/issues/943)) ([875513f](https://github.com/harttle/liquidjs/commit/875513f4c5136bed0c64562cccabb21a7db8d36c))
+
+# [10.28.0](https://github.com/harttle/liquidjs/compare/v10.27.2...v10.28.0) (2026-08-01)
+
+
+### Bug Fixes
+
+* **date:** %s returns Unix epoch unaffected by display timezone ([#932](https://github.com/harttle/liquidjs/issues/932)) ([39c8743](https://github.com/harttle/liquidjs/commit/39c87437c5ef38ede9a208c9d55cd13231c6c023)), closes [#931](https://github.com/harttle/liquidjs/issues/931)
+
+
+### Features
+
+* Add support of inner expressions enclosed by parentheses ([#863](https://github.com/harttle/liquidjs/issues/863)) ([afa5f54](https://github.com/harttle/liquidjs/commit/afa5f5400428fc1ec935aca0282e579224660c95))
+
+## [10.27.2](https://github.com/harttle/liquidjs/compare/v10.27.1...v10.27.2) (2026-07-09)
+
+
+### Bug Fixes
+
+* charge join/json/inspect filters by produced output size ([#925](https://github.com/harttle/liquidjs/issues/925)) ([7ab49f9](https://github.com/harttle/liquidjs/commit/7ab49f999ac045ec1e87f3a7a9fd68dd9e8602b3))
+* **date:** zero-pad milliseconds when formatting %N fractional seconds ([#929](https://github.com/harttle/liquidjs/issues/929)) ([2634f9d](https://github.com/harttle/liquidjs/commit/2634f9de7b1228cd887b7cab880af8a795c77053))
+* enforce ownPropertyOnly for inherited array indices ([#924](https://github.com/harttle/liquidjs/issues/924)) ([552819a](https://github.com/harttle/liquidjs/commit/552819a84b80c62306fe61072628a756272dc749))
+* **filters:** modulo should follow divisor sign for negative operands ([#922](https://github.com/harttle/liquidjs/issues/922)) ([568bd5f](https://github.com/harttle/liquidjs/commit/568bd5f9cb99f596292c09fd70b00284b8216f0c))
+* **filters:** return empty for out-of-range slice begin or negative length ([#928](https://github.com/harttle/liquidjs/issues/928)) ([f9a1316](https://github.com/harttle/liquidjs/commit/f9a1316d161f4f20018c833160f42dfcf0cde507))
+
+## [10.27.1](https://github.com/harttle/liquidjs/compare/v10.27.0...v10.27.1) (2026-06-23)
+
+
+### Bug Fixes
+
+* improve round function; improvement to [#873](https://github.com/harttle/liquidjs/issues/873) ([#901](https://github.com/harttle/liquidjs/issues/901)) ([956b51e](https://github.com/harttle/liquidjs/commit/956b51ea953eb52d9eba7409b7f51e379023fec4))
+* **security:** charge pop filter allocation to memoryLimit ([#907](https://github.com/harttle/liquidjs/issues/907)) ([8a0c74a](https://github.com/harttle/liquidjs/commit/8a0c74a7fcb1671aa1dcb71ec82ba0602dc90d04))
+* **strip_html:** infinite loop for strip_html ([5c3522f](https://github.com/harttle/liquidjs/commit/5c3522f33928aae66f0fe85c36e1d9015c768fe2))
+
+
+### Performance Improvements
+
+* **parser:** memoize createTrie to avoid rebuilding tries per Tokenizer ([#911](https://github.com/harttle/liquidjs/issues/911)) ([3a0d80d](https://github.com/harttle/liquidjs/commit/3a0d80d1f4526af0fbca2bb2e0a9c51669d2fd3e))
+
+# [10.27.0](https://github.com/harttle/liquidjs/compare/v10.26.0...v10.27.0) (2026-05-15)
+
+
+### Features
+
+* **context:** null-prototype scope frames via createScope ([#899](https://github.com/harttle/liquidjs/issues/899)) ([47d3f1b](https://github.com/harttle/liquidjs/commit/47d3f1b1cf33be91fe587821f288d1c9d8e1ace7))
+
+# [10.26.0](https://github.com/harttle/liquidjs/compare/v10.25.7...v10.26.0) (2026-05-14)
+
+
+### Bug Fixes
+
+* **date:** cap strftime widths and account padding in memoryLimit ([#895](https://github.com/harttle/liquidjs/issues/895)) ([3129d46](https://github.com/harttle/liquidjs/commit/3129d46dc95efa357b00e5a57ee1af80a13d72ed))
+* enforce renderLimit for empty renderTemplates calls ([#894](https://github.com/harttle/liquidjs/issues/894)) ([5b9c346](https://github.com/harttle/liquidjs/commit/5b9c3469085e01c79e2d0af28e2a13f730e1793d))
+* propagate ownPropertyOnly into Context.spawn() for {% render %} ([#893](https://github.com/harttle/liquidjs/issues/893)) ([dbbf628](https://github.com/harttle/liquidjs/commit/dbbf6288030591bf6da28d8c1cce5a17bca97bb6))
+* **security:** block Object.prototype filter/tag lookups (RCE) ([#897](https://github.com/harttle/liquidjs/issues/897)) ([457fae0](https://github.com/harttle/liquidjs/commit/457fae0736c3ec862539b9dbf7f477e6c08fb6c6))
+* strip html newline tags ([#892](https://github.com/harttle/liquidjs/issues/892)) ([26ea285](https://github.com/harttle/liquidjs/commit/26ea2856c7a90aec892b98d94a9b7a3e18539045))
+* **strip_html:** rewrite as linear single-pass scan to avoid ReDoS ([#896](https://github.com/harttle/liquidjs/issues/896)) ([3616a74](https://github.com/harttle/liquidjs/commit/3616a744b9abeb425c217b340a2397d46176afb8))
+
+
+### Features
+
+* add sha256 and hmac_sha256 filters for cryptographic operations ([#889](https://github.com/harttle/liquidjs/issues/889)) ([1c816d4](https://github.com/harttle/liquidjs/commit/1c816d4fc3bcd2cba011f7a84f56a4251fca0622))
+
 ## [10.25.7](https://github.com/harttle/liquidjs/compare/v10.25.6...v10.25.7) (2026-04-23)
 
 

README.md

@@ -1,72 +1,86 @@
-# liquidjs
+# LiquidJS
+
+A simple, expressive, extensible Liquid template engine for JavaScript — Shopify, Jekyll and GitHub Pages compatible, for Node.js, browsers, and the CLI, with TypeScript support.
+
 [![npm version](https://img.shields.io/npm/v/liquidjs.svg?logo=npm&style=flat-square)](https://www.npmjs.org/package/liquidjs)
 [![npm downloads](https://img.shields.io/npm/dm/liquidjs.svg?style=flat-square)](https://www.npmjs.org/package/liquidjs)
-[![Coverage](https://img.shields.io/coveralls/harttle/liquidjs.svg?style=flat-square)](https://coveralls.io/github/harttle/liquidjs?branch=master)
 [![Build Status](https://img.shields.io/github/actions/workflow/status/harttle/liquidjs/ci-build.yml?branch=master&style=flat-square)](https://github.com/harttle/liquidjs/actions/workflows/ci-build.yml?query=branch%3Amaster)
-[![DUB license](https://img.shields.io/dub/l/vibe-d.svg?style=flat-square)](https://github.com/harttle/liquidjs/blob/master/LICENSE)
-[![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg?style=flat-square)](https://github.com/harttle/liquidjs)
+[![Coverage](https://img.shields.io/coveralls/harttle/liquidjs.svg?style=flat-square)](https://coveralls.io/github/harttle/liquidjs?branch=master)
+[![License: MIT](https://img.shields.io/github/license/harttle/liquidjs?style=flat-square)](https://github.com/harttle/liquidjs/blob/master/LICENSE)
 
-A simple, expressive and safe [Shopify][shopify/liquid] / GitHub Pages compatible template engine in pure JavaScript.
-**The purpose of this repo** is to provide a standard Liquid implementation for the JavaScript community so that [Jekyll sites](https://jekyllrb.com), [GitHub Pages](https://pages.github.com/) and [Shopify templates](https://themes.shopify.com/) can be ported to Node.js without pain.
+[Documentation][doc] · [Playground](https://liquidjs.com/playground.html) · [Setup guide][setup] · [Contributing][contribution]
 
-* [Documentation][doc]
-* Please star [LiquidJS on GitHub][github]!
-* Financial support via [GitHub Sponsors](https://github.com/sponsors/harttle).
+<a href="https://liquidjs.com/playground.html">
+  <img src="docs/source/playground-demo.gif" alt="LiquidJS playground: edit a template and context, see live HTML output" width="980" style="display: block; margin: 0 auto;" />
+</a>
 
-<p align="center"><a href="https://liquidjs.com"><img height="155px" width="155px" src="https://liquidjs.com/icon/mstile-310x310.png" alt="logo"></a></p>
+<p align="center"><sub>Try the <a href="https://liquidjs.com/playground.html">online playground</a>.</sub></p>
 
-## What's it like?
+## Quick start
 
-Basically there're two types of Liquid syntax: tags enclosed by `{% %}` and outputs enclosed by `{{ }}`. A Liquid template looks like:
+```js
+import { Liquid } from 'liquidjs'
 
-```liquid
-{% if username %}
-  {{ username | append: ", welcome to LiquidJS!" | capitalize }}
-{% endif %}
+const engine = new Liquid()
+const html = await engine.parseAndRender(
+  'Hello, {{ name | capitalize }}!',
+  { name: 'liquid' }
+)
+//=> 'Hello, Liquid!'
 ```
 
-[A live demo](https://liquidjs.com/playground.html) is also available and here's a [quick tutorial](https://liquidjs.com/tutorials/intro-to-liquid.html) for Liquid syntax.
-
-
 ## Installation
 
-Install from npm in Node.js:
+**Node.js**
 
 ```bash
 npm install liquidjs
 ```
 
-Or use the UMD bundle from jsDelivr:
+**Browser** (jsDelivr UMD bundle)
 
 ```html
 <script src="https://cdn.jsdelivr.net/npm/liquidjs/dist/liquid.browser.min.js"></script>
 ```
 
-Or render directly from CLI using npx:
+**CLI**
 
 ```bash
-npx liquidjs --template 'Hello, {{ name }}!' --context '{"name": "Snake"}'
+npx liquidjs --template 'Hello, {{ name }}!' --context '{"name": "Liquid"}'
 ```
 
-For more details, refer to the [Setup Guide][setup].
+See the [setup guide][setup] for partials, layouts, caching, and other options.
 
-## Who's Using LiquidJS?
+## Used by
 
-- [Eleventy](https://www.11ty.dev/): Eleventy, a simpler static site generator.
-- [Github Docs](https://github.com/github/docs): The open-source repo for docs.github.com.
-- [Kibana](https://github.com/elastic/kibana): Elastic's analytics and visualization platform for Elasticsearch; workflow features use LiquidJS for Liquid templates.
-- [Opensense](https://www.opensense.com/): The smarter way to send email.
-- [Directus](https://docs.directus.io/): an instant REST+GraphQL API and intuitive no-code data collaboration app for any SQL database.
-- [Rock](https://www.rockrms.com/): An open source CMS, Relationship Management System (RMS) and Church Management System (ChMS) all rolled into one.
-- [Mitosis](https://github.com/BuilderIO/mitosis): Write components once, run everywhere. Compiles to React, Vue, Qwik, Solid, Angular, Svelte, and more.
-- [Pattern Lab](https://patternlab.io/): a frontend workshop environment that helps you build, view, test, and showcase your design system's UI components.
-- [Builder.io](https://www.builder.io/m/developers): the first and only headless CMS with a visual editor that lets you drag and drop with your components, directly within your current site or app. Completely API-driven, for cleaner code and simpler workflows.
-- [Microsoft Power Pages](https://learn.microsoft.com/en-us/power-pages/introduction): a secure, enterprise-grade, low-code software as a service (SaaS) platform for creating, hosting, and administering modern external-facing business websites.
-- [Azure API Management developer portal](https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-developer-portal): an automatically generated, fully customizable website with the documentation of your APIs.
-- [WISMOlabs](https://wismolabs.com/): Post Purchase Experience platform for eCommerce retailers enhancing customer satisfaction by using LiquidJS to provide customizable post-purchase experiences through programmable email, SMS, order tracking pages, and webhooks.
-- [Freshet](https://chromewebstore.google.com/detail/freshet/mpclplhdencffbilobpcapccnihpelcg): *JSON in, page out* — a Chrome extension that uses LiquidJS templates per URL pattern, so the JSON becomes a rendered, useful page.
+<!-- USED-BY-BEGIN -->
+<p align="center" style="line-height: 2.5;">
+  <a href="https://www.11ty.dev/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/35147177?v=4&s=100" height="80" style="vertical-align: middle;" alt="Eleventy" title="Eleventy"/></a>
+  <a href="https://www.opensense.com/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://images.opencollective.com/opensense-inc/bf840ae/logo/256.png?height=100" height="80" style="vertical-align: middle;" alt="Opensense" title="Opensense"/></a>
+  <a href="https://www.microsoft.com/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/6154722?v=4&s=100" height="80" style="vertical-align: middle;" alt="Power Pages, Azure API Management developer portal" title="Power Pages, Azure API Management developer portal"/></a>
+  <a href="https://docs.github.com/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/9919?v=4&amp;s=100" height="80" style="vertical-align: middle;" alt="GitHub Docs" title="GitHub Docs"/></a>
+  <a href="https://github.com/elastic/kibana" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/6764390?v=4&s=100" height="80" style="vertical-align: middle;" alt="Kibana" title="Kibana"/></a>
+  <a href="https://www.shopify.com/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/8085?v=4&amp;s=100" height="80" style="vertical-align: middle;" alt="Shopify CLI, Checkout Blocks" title="Shopify CLI, Checkout Blocks"/></a>
+  <a href="https://customer.io/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/1152079?v=4&s=100" height="80" style="vertical-align: middle;" alt="Customer IO" title="Customer IO"/></a>
+  <br/>
+  <a href="https://syntax.fm/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/130389858?v=4&s=100" height="80" style="vertical-align: middle;" alt="Syntax Podcast" title="Syntax Podcast"/></a>
+  <a href="https://www.testmuai.com/?utm_medium=sponsor&utm_source=liquidjs" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/27130435?s=200&v=4" width="80" style="vertical-align: middle;" alt="TestMu AI" title="TestMu AI"/></a>
+  <a href="https://chudovo.com/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://images.opencollective.com/Chudovo/avatar/256.png?height=100" width="160" style="vertical-align: middle;background: white;padding: 8px 16px;" alt="Chudovo" title="Chudovo"/></a>
+  <a href="https://www.pakstyle.pk/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://images.opencollective.com/pakstyle/2b81605/logo/256.png?height=100" height="80" style="vertical-align: middle;" alt="PakStyle.pk" title="PakStyle.pk"/></a>
+  <a href="https://www.escorta.com/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://images.opencollective.com/escortacom/avatar/256.png?height=100" height="45" style="vertical-align: middle;" alt="EscortA.com" title="EscortA.com"/></a>
+  <a href="https://opencollective.com/touchless" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://images.opencollective.com/touchless/273bc74/logo/256.png?height=100" height="80" style="vertical-align: middle;" alt="Touchless" title="Touchless"/></a>
+  <br/>
+  <a href="https://www.dropkiq.com/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://images.opencollective.com/1bertlol/43a8ea8/logo/256.png?height=100" height="80" style="vertical-align: middle;" alt="Dropkiq" title="Dropkiq"/></a>
+  <a href="https://directus.io/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/15967950?v=4&amp;s=100" height="80" style="vertical-align: middle;" alt="Directus" title="Directus"/></a>
+  <a href="https://www.builder.io/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F51a002f4a17f4fc4a829b8891a1c25ee" height="80" style="vertical-align: middle;" alt="Builder.io, Mitosis" title="Builder.io, Mitosis"/></a>
+  <a href="https://patternlab.io/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/4733935?v=4&amp;s=100" height="80" style="vertical-align: middle;" alt="Pattern Lab" title="Pattern Lab"/></a>
+  <a href="https://www.rockrms.com/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://www.rockrms.com/GetImage.ashx?id=72533" height="80" style="vertical-align: middle;" alt="Rock RMS" title="Rock RMS"/></a>
+  <a href="https://wismolabs.com/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://cdn-ldlap.nitrocdn.com/DsLJMZpUUekfsitqBnNmsRAnzbwPoIzE/assets/images/optimized/rev-5df8687/wismolabs.com/wp-content/uploads/2023/03/favicon-300x300.png" height="80" style="vertical-align: middle;" alt="WISMOlabs" title="WISMOlabs"/></a>
+  <a href="https://chromewebstore.google.com/detail/freshet/mpclplhdencffbilobpcapccnihpelcg" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://raw.githubusercontent.com/MattAltermatt/freshet/main/public/icon-128.png" height="80" style="vertical-align: middle;" alt="Freshet" title="Freshet"/></a>
+</p>
+<!-- USED-BY-END -->
 
-Feel free to create a PR or contact me to add your use case into this list!
+Products and projects running on LiquidJS. [Open a PR](https://github.com/harttle/liquidjs/edit/master/README.md) to add yours.
 
 ## Financial Support
 
@@ -78,7 +92,7 @@ If you personally love LiquidJS or it's benefiting your business, please conside
   <a href="https://www.opensense.com/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://images.opencollective.com/opensense-inc/bf840ae/logo/256.png?height=100" height="80" style="vertical-align: middle;" alt="Opensense Inc." title="Opensense"/></a>
   <a href="https://github.com/microsoft" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/6154722?v=4&s=100" height="80" style="vertical-align: middle;" alt="Microsoft" title="Microsoft"/></a>
   <a href="https://sentry.io/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/1396951?v=4&s=100" height="80" style="vertical-align: middle;" alt="Sentry" title="Sentry"/></a>
-  <a href="https://www.checkoutblocks.com/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/114603307?v=4&s=100" height="80" style="vertical-align: middle;" alt="Checkout Blocks" title="Checkout Blocks"/></a>
+  <a href="https://github.com/Checkout-Blocks" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/114603307?v=4&s=100" height="80" style="vertical-align: middle;" alt="Checkout Blocks" title="Checkout Blocks"/></a>
   <a href="https://customer.io/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/1152079?v=4&s=100" height="80" style="vertical-align: middle;" alt="Customer IO" title="Customer IO"/></a>
   <a href="https://syntax.fm/" style="display: inline-block; vertical-align: middle; margin: 8px;"><img src="https://avatars.githubusercontent.com/u/130389858?v=4&s=100" height="80" style="vertical-align: middle;" alt="Syntax Podcast" title="Syntax Podcast"/></a>
   <br/>
@@ -226,6 +240,11 @@ Want to contribute? see [Contribution Guidelines][contribution]. Thanks goes to
       <td align="center" valign="top" width="14.28%"><a href="https://github.com/talboren"><img src="https://avatars.githubusercontent.com/u/68807791?v=4?s=100" width="100px;" alt="Tal"/><br /><sub><b>Tal</b></sub></a><br /><a href="https://github.com/harttle/liquidjs/commits?author=talboren" title="Code">💻</a></td>
       <td align="center" valign="top" width="14.28%"><a href="https://filonov.dev"><img src="https://avatars.githubusercontent.com/u/813224?v=4?s=100" width="100px;" alt="Vladimir Filonov"/><br /><sub><b>Vladimir Filonov</b></sub></a><br /><a href="https://github.com/harttle/liquidjs/commits?author=VladimirFilonov" title="Code">💻</a></td>
     </tr>
+    <tr>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/spokodev"><img src="https://avatars.githubusercontent.com/u/239690017?v=4?s=100" width="100px;" alt="spokodev"/><br /><sub><b>spokodev</b></sub></a><br /><a href="https://github.com/harttle/liquidjs/commits?author=spokodev" title="Code">💻</a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/YacovGold"><img src="https://avatars.githubusercontent.com/u/8984042?v=4?s=100" width="100px;" alt="YacovGold"/><br /><sub><b>YacovGold</b></sub></a><br /><a href="https://github.com/harttle/liquidjs/commits?author=YacovGold" title="Code">💻</a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/sarathfrancis90"><img src="https://avatars.githubusercontent.com/u/9289498?v=4?s=100" width="100px;" alt="Sarath Francis"/><br /><sub><b>Sarath Francis</b></sub></a><br /><a href="https://github.com/harttle/liquidjs/commits?author=sarathfrancis90" title="Code">💻</a></td>
+    </tr>
   </tbody>
 </table>
 
@@ -234,8 +253,10 @@ Want to contribute? see [Contribution Guidelines][contribution]. Thanks goes to
 
 <!-- ALL-CONTRIBUTORS-LIST:END -->
 
-[shopify/liquid]: https://shopify.github.io/liquid/
-[plugins]: https://liquidjs.com/tutorials/plugins.html#Plugin-List
+## License
+
+[MIT](LICENSE) © [Jun Yang](https://github.com/harttle)
+
 [setup]: https://liquidjs.com/tutorials/setup.html
 [doc]: https://liquidjs.com
 [github]: https://github.com/harttle/liquidjs

SECURITY.md

@@ -6,8 +6,10 @@ Only the latest major version is supported with security updates. It can be chan
 
 ## Reporting a Vulnerability
 
-Please contact harttleharttle@gmail.com to report a vulnerability or change request.
+**Please do not report security vulnerabilities through public GitHub issues.**
 
-- If the vulnerability in question affects common use cases, it will be treated as a bug and fixed very soon (typically within 1 week).
+Report them via [GitHub Security Advisories — Report a vulnerability](https://github.com/harttle/liquidjs/security/advisories/new).
+
+- If the vulnerability in question affects common use cases, it will be treated as a bug and fixed very soon (typically within a month).
 - Otherwise, it'll be scheduled in the same priority of feature request (which is lower than bugs).
-- If the request is declined, you'll receive a reply email anyway (most likely there will be a discussion).
+- If the request is declined, you'll receive a reply anyway (most likely there will be a discussion).

bin/build-changelog.js

@@ -18,7 +18,5 @@ content = content
   .replace(/\{\{/g, '{% raw %}{{{% endraw %}')
 
 const enFrontmatter = '---\ntitle: Changelog\nauto: true\n---\n\n'
-const zhFrontmatter = '---\ntitle: 更新日志\nauto: true\n---\n\n'
 
 fs.writeFileSync(path.join(root, 'docs/source/tutorials/changelog.md'), enFrontmatter + content)
-fs.writeFileSync(path.join(root, 'docs/source/zh-cn/tutorials/changelog.md'), zhFrontmatter + content)

bin/build-contributors.js

@@ -33,7 +33,9 @@ function transformFinancial (html) {
 
 const allContributors = transformContributors(extractSection(readme, 'ALL-CONTRIBUTORS-LIST:START', 'ALL-CONTRIBUTORS-LIST:END'))
 const financialContributors = transformFinancial(extractSection(readme, 'FINANCIAL-CONTRIBUTORS-BEGIN', 'FINANCIAL-CONTRIBUTORS-END'))
+const usedBy = transformFinancial(extractSection(readme, 'USED-BY-BEGIN', 'USED-BY-END'))
 
 const outDir = path.join(root, 'docs/themes/navy/layout/partial')
 fs.writeFileSync(path.join(outDir, 'all-contributors.swig'), allContributors)
 fs.writeFileSync(path.join(outDir, 'financial-contributors.swig'), financialContributors)
+fs.writeFileSync(path.join(outDir, 'used-by.swig'), usedBy)

docs/_config.yml

@@ -1,10 +1,8 @@
 title: LiquidJS
-subtitle: "A simple, expressive and safe template engine."
-description: "LiquidJS is a simple, expressive and safe Shopify / GitHub Pages compatible template engine in pure JavaScript."
+subtitle: "A simple, expressive, extensible Liquid template engine for JavaScript"
+description: "A simple, expressive, extensible Liquid template engine for JavaScript — Shopify, Jekyll and GitHub Pages compatible, for Node.js, browsers, and the CLI, with TypeScript support."
 author: Harttle
-language:
-  - en
-  - zh-cn
+language: en
 timezone: UTC
 
 url: https://liquidjs.com

docs/scripts/helpers.js

@@ -2,6 +2,8 @@
 
 'use strict'
 
+require('./prism-bash-extend')
+
 const { resolve, basename } = require('path')
 const { readFileSync } = require('fs')
 const cheerio = require('cheerio')

docs/scripts/prism-bash-extend.js

@@ -0,0 +1,34 @@
+'use strict'
+
+/**
+ * Extend Prism's bash grammar with extra CLI commands for docs code blocks.
+ * Hexo loads scripts from docs/scripts/ during init, before `hexo generate`
+ * highlights fenced code via syntax_highlighter: prismjs.
+ *
+ * Bash highlights known commands via a large hard-coded regex (see prism-bash).
+ * insertBefore is the supported extension point when a command is not in that list.
+ * Add names to EXTRA_BASH_COMMANDS as needed.
+ *
+ * After editing this file, run `npx hexo clean` before generate/serve so
+ * Hexo re-highlights cached pages (db.json does not invalidate on script changes).
+ */
+const EXTRA_BASH_COMMANDS = [
+  'npx'
+]
+
+const Prism = require('prismjs')
+require('prismjs/components/prism-bash')
+
+const escaped = EXTRA_BASH_COMMANDS.map((cmd) =>
+  cmd.replace(/[.*+?^${}()|[\]\\]/g, '\\$&')
+)
+
+Prism.languages.insertBefore('bash', 'function', {
+  'cli-command': {
+    pattern: new RegExp(
+      `(^|[\\s;|&]|[<>]\\()(?:${escaped.join('|')})(?=$|[)\\s;|&])`
+    ),
+    lookbehind: true,
+    alias: ['builtin', 'class-name']
+  }
+})

docs/source/_data/languages.yml

@@ -1,3 +1 @@
 en: English
-zh-cn:
-  name: 简体中文

docs/source/_data/news.yml

@@ -1,24 +0,0 @@
--
-  url: https://opencollective.com/liquidjs/#section-contribute
-  date: '2020-02-26'
-  title:
-    zh-cn: '赞助人：第一个 backer 通过 Open Collective 贡献于 LiquidJS。'
-    en: 'Backers: the first backer contributed to LiquidJS via Open Collective.'
--
-  url: https://github.com/harttle/liquidjs/pull/202
-  date: '2020-03-11'
-  title:
-    zh-cn: '内存优化：用更精细的手法重写了解析器，来避免临时字符串的生成，内存占用降低 57.7% 以上。'
-    en: 'Memory Optimization: a more elaborate parser reducing the memory footprint by 57.7%.'
--
-  url: https://github.com/harttle/liquidjs/pull/205
-  date: '2020-03-15'
-  title:
-    zh-cn: '性能提升：引入 AST 并重新设计 Token 类型系统，使渲染性能平均提升 100.3%。'
-    en: 'Performance Boost: a simple AST to improve render performance by 100.3%.'
--
-  url: https://github.com/harttle/liquidjs/milestone/3?closed=1
-  date: '2021-09-30'
-  title:
-    zh-cn: '流式渲染：4 倍渲染速度，并增加了对流式渲染的支持。'
-    en: 'Streamed Rendering: now render is 4x faster and support streamed rendering.'

docs/source/_data/sidebar.yml

@@ -19,7 +19,7 @@ tutorials:
     plugins: plugins.html
     operators: operators.html
     truth: truthy-and-falsy.html
-    dos: dos.html
+    security_model: security-model.html
     static_analysis: static-analysis.html
   miscellaneous:
     migration9: migrate-to-9.html
@@ -94,6 +94,7 @@ filters:
   sort: sort.html
   sort_natural: sort_natural.html
   split: split.html
+  squish: squish.html
   strip: strip.html
   strip_html: strip_html.html
   strip_newlines: strip_newlines.html
@@ -114,7 +115,7 @@ filters:
 
 tags:
   overview: overview.html
-  "#": inline_comment.html
+  "# (inline comment)": inline_comment.html
   assign: assign.html
   capture: capture.html
   case: case.html

docs/source/filters/date.md

@@ -3,18 +3,18 @@ title: date
 ---
 {% since %}v1.9.1{% endsince %}
 
-Date filter is used to convert a timestamp into the specified format.
+The `date` filter is used to convert a timestamp into the specified format.
 
-* LiquidJS tries to conform to Shopify/Liquid, which uses Ruby's core [Time#strftime(string)](https://www.ruby-doc.org/core/Time.html#method-i-strftime). There're differences with [Ruby's format flags](https://ruby-doc.org/core/strftime_formatting_rdoc.html):
+* LiquidJS tries to conform to Shopify/Liquid, which uses Ruby's core [Time#strftime(string)](https://www.ruby-doc.org/core/Time.html#method-i-strftime). There are differences with [Ruby's format flags](https://ruby-doc.org/core/strftime_formatting_rdoc.html):
   * `%Z` (since v10.11.1) is replaced by the passed-in timezone name from `LiquidOption` or in-place value (see TimeZone below). If passed-in timezone is an offset number instead of string, it'll behave like `%z`. If there's none passed-in timezone, it returns [the runtime's default time zone](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat/resolvedOptions#timezone).
   * LiquidJS provides an additional `%q` flag for date ordinals. e.g. `{{ '2023/02/02' | date: '%d%q of %b'}}` => `02nd of Feb`
-* Date literals are firstly converted to `Date` object via [new Date()][jsDate], that means literal values are considered in runtime's time zone by default.
+* Date literals are first converted to a `Date` object via [new Date()][jsDate], which means literal values are considered in the runtime's time zone by default.
 * The format filter argument is optional:
     * If not provided, it defaults to `%A, %B %-e, %Y at %-l:%M %P %z`.
     * The above default can be overridden by [`dateFormat`](/api/interfaces/LiquidOptions.html#dateFormat) LiquidJS option.
 * LiquidJS `date` supports locale specific weekdays and month names, which will fallback to English where `Intl` is not supported.
     * Ordinals (`%q`) and Jekyll specific date filters are English-only.
-    * [`locale`](/api/interfaces/LiquidOptions.html#locale) can be set when creating Liquid instance. Defaults to `Intl.DateTimeFormat().resolvedOptions.locale`).
+    * [`locale`](/api/interfaces/LiquidOptions.html#locale) can be set when creating a Liquid instance. Defaults to `Intl.DateTimeFormat().resolvedOptions().locale`.
 
 ### Examples
 ```liquid
@@ -26,14 +26,15 @@ Date filter is used to convert a timestamp into the specified format.
 ```
 
 # TimeZone
-* During output, LiquidJS uses local timezone which can override by:
+* During output, LiquidJS uses the local timezone, which can be overridden by:
     * setting a timezone in-place when calling `date` filter, or
     * setting the [`timezoneOffset`](/api/interfaces/LiquidOptions.html#timezoneOffset) LiquidJS option
-        * It defaults to runtime's time one.
+        * It defaults to the runtime's timezone.
         * Offset can be set as,
             * minutes: `-360` means `'+06:00'` and `360` means `'-06:00'`
             * timeZone ID: `Asia/Colombo` or `America/New_York`
     * See [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) for TZ database values
+* `%s` (seconds since the Unix epoch) identifies an instant rather than a wall-clock time, so it's not affected by the display timezone.
 
 ### Examples
 ```liquid

docs/source/filters/json.md

@@ -4,7 +4,7 @@ title: json
 
 {% since %}v9.10.0{% endsince %}
 
-Convert values to string via `JSON.stringify()`, for debug purpose.
+Convert values to string via `JSON.stringify()`, for debugging purposes.
 
 Input
 ```liquid

docs/source/filters/overview.md

@@ -5,17 +5,17 @@ description: Description and demo for each Liquid filter
 
 LiquidJS implements business-logic independent filters that are typically implemented in [shopify/liquid][shopify/liquid]. This section contains the specification and demos for all the filters implemented by LiquidJS.
 
-There's 40+ filters supported by LiquidJS. These filters can be categorized into these groups:
+There are 40+ filters supported by LiquidJS. These filters can be categorized into these groups:
 
 Categories | Filters
 --- | ---
-Math | plus, minus, modulo, times, floor, ceil, round, divided_by, abs, at_least, at_most
-String | append, prepend, capitalize, upcase, downcase, strip, lstrip, rstrip, strip_newlines, split, replace, replace_first, replace_last,remove, remove_first, remove_last, truncate, truncatewords, normalize_whitespace, number_of_words, array_to_sentence_string
-HTML/URI | escape, escape_once, url_encode, url_decode, strip_html, newline_to_br, xml_escape, cgi_escape, uri_escape, slugify
-Array | slice, map, sort, sort_natural, uniq, where, where_exp, group_by, group_by_exp, find, find_exp, first, last, join, reverse, concat, compact, size, push, pop, shift, unshift
-Date | date, date_to_xmlschema, date_to_rfc822, date_to_string, date_to_long_string
-Misc | default, json, jsonify, inspect, raw, to_integer
-Base64 | base64_encode, base64_decode
-Crypto | sha256, hmac_sha256
+Math | `plus`, `minus`, `modulo`, `times`, `floor`, `ceil`, `round`, `divided_by`, `abs`, `at_least`, `at_most`
+String | `append`, `prepend`, `capitalize`, `upcase`, `downcase`, `strip`, `lstrip`, `rstrip`, `strip_newlines`, `split`, `replace`, `replace_first`, `replace_last`,`remove`, `remove_first`, `remove_last`, `truncate`, `truncatewords`, `normalize_whitespace`, `number_of_words`, `array_to_sentence_string`
+HTML/URI | `escape`, `escape_once`, `url_encode`, `url_decode`, `strip_html`, `newline_to_br`, `xml_escape`, `cgi_escape`, `uri_escape`, `slugify`
+Array | `slice`, `map`, `sort`, `sort_natural`, `uniq`, `where`, `where_exp`, `group_by`, `group_by_exp`, `find`, `find_exp`, `first`, `last`, `join`, `reverse`, `concat`, `compact`, `size`, `push`, `pop`, `shift`, `unshift`
+Date | `date`, `date_to_xmlschema`, `date_to_rfc822`, `date_to_string`, `date_to_long_string`
+Misc | `default`, `json`, `jsonify`, `inspect`, `raw`, `to_integer`
+Base64 | `base64_encode`, `base64_decode`
+Crypto | `sha256`, `hmac_sha256`
 
 [shopify/liquid]: https://github.com/Shopify/liquid

docs/source/filters/squish.md

@@ -0,0 +1,18 @@
+---
+title: squish
+---
+
+{% since %}v10.28.0{% endsince %}
+
+Removes leading and trailing whitespace from a string, and replaces every run of whitespace inside it with a single space.
+
+Input
+```liquid
+{{ "  Hello   there,
+    Major Tom.  " | squish }}
+```
+
+Output
+```text
+Hello there, Major Tom.
+```

docs/source/filters/strip_html.md

@@ -6,6 +6,10 @@ title: strip_html
 
 Removes any HTML tags from a string.
 
+{% note warn Not safe for HTML output %}
+This filter removes tags by string scanning; it does not parse HTML5 the way a browser does, and it is not a sanitizer. The result may still be unsafe when inserted into HTML. Use [escape][escape], [escape_once][escape_once], or [`outputEscape: "escape"`][outputEscape] for untrusted output.
+{% endnote %}
+
 Input
 ```liquid
 {{ "Have <em>you</em> read <strong>Ulysses</strong>?" | strip_html }}
@@ -15,3 +19,7 @@ Output
 ```text
 Have you read Ulysses?
 ```
+
+[escape]: ./escape.html
+[escape_once]: ./escape.html
+[outputEscape]: ../tutorials/options.html#outputEscape

docs/source/filters/truncate.md

@@ -36,7 +36,7 @@ Ground control, and so on
 
 ## No ellipsis
 
-You can truncate to the exact number of characters specified by the first argument and avoid showing trailing characters by passing a blank string as the second argument:
+You can `truncate` to the exact number of characters specified by the first argument and avoid showing trailing characters by passing a blank string as the second argument:
 
 Input
 ```liquid

docs/source/index.pug

@@ -1,29 +1,27 @@
 layout: index
-description: LiquidJS is a simple, expressive and safe Shopify / GitHub Pages compatible template engine in pure JavaScript.
-subtitle: A simple, expressive and safe template engine.
 ---
 ul#intro-feature-list
   li.intro-feature-wrap
     .intro-feature
       .intro-feature-icon
         i.icon-shield
-      h3.intro-feature-title Safe Rendering
-      p.intro-feature-desc Liquid templates are highly readable and fault-tolerant thus suitable for designers and customers. Operators and expressions are parsed to AST and no #[code eval] or #[code new Function] are used. 
+      h3.intro-feature-title Safe & Typed
+      p.intro-feature-desc Templates are readable and fault-tolerant, parsed to an AST with no #[code eval] or #[code new Function]. The whole repo is written in TypeScript strict mode, so types stay precise and docs accurate.
   li.intro-feature-wrap
     .intro-feature
       .intro-feature-icon
         i.icon-rocket
       h3.intro-feature-title Pure JavaScript
-      p.intro-feature-desc Written with pure JavaScript with no native bindings, available in both Node.js and browsers. All of the CMD, ESM and CJS bundles are available on CDN.
+      p.intro-feature-desc Written in pure JavaScript with no native bindings, running in both Node.js and the browser. The CMD, ESM and CJS bundles are all available on CDN.
   li.intro-feature-wrap
     .intro-feature
       .intro-feature-icon
         i.icon-shopify
-      h3.intro-feature-title Shopify Compatible
-      p.intro-feature-desc All filters and tags from Ruby #[a(href="https://github.com/shopify/liquid") shopify/liquid] are supported by LiquidJS. #[a(href="https://jekyllrb.com/") Jekyll sites], #[a(href="https://pages.github.com/") GitHub Pages] and #[a(href="https://themes.shopify.com/") Shopify templates] can be ported to Node.js without pain.
+      h3.intro-feature-title Shopify & Jekyll
+      p.intro-feature-desc All filters and tags from Ruby #[a(href="https://github.com/shopify/liquid") shopify/liquid] are supported, so #[a(href="https://themes.shopify.com/") Shopify templates] work out of the box — as do #[a(href="https://jekyllrb.com/") Jekyll] sites and #[a(href="https://pages.github.com/") GitHub Pages].
   li.intro-feature-wrap
     .intro-feature
       .intro-feature-icon
-        i.icon-typescript
-      h3.intro-feature-title TypeScript Strict
-      p.intro-feature-desc The whole repo is re-written in TypeScript strict mode to ensure a smooth experience using this lib and the document is precise and always up to date.
+        i.icon-network
+      h3.intro-feature-title Streaming
+      p.intro-feature-desc Render directly to a Node.js stream with #[code renderToNodeStream], emitting output as it's produced — for a faster time to first byte and low memory usage on large pages.

docs/source/llms.txt

@@ -0,0 +1,28 @@
+# LiquidJS
+
+> A simple, expressive, extensible Liquid template engine for JavaScript
+
+## Tutorials
+
+- [Introduction to Liquid](https://liquidjs.com/tutorials/intro-to-liquid.html)
+- [Setup](https://liquidjs.com/tutorials/setup.html)
+- [Options](https://liquidjs.com/tutorials/options.html)
+- [Render files](https://liquidjs.com/tutorials/render-file.html)
+- [Partials and layouts](https://liquidjs.com/tutorials/partials-and-layouts.html)
+- [Express.js](https://liquidjs.com/tutorials/use-in-expressjs.html)
+- [Register filters and tags](https://liquidjs.com/tutorials/register-filters-tags.html)
+- [Plugins](https://liquidjs.com/tutorials/plugins.html)
+- [Sync and async](https://liquidjs.com/tutorials/sync-and-async.html)
+- [Operators](https://liquidjs.com/tutorials/operators.html)
+- [Truthy and falsy](https://liquidjs.com/tutorials/truthy-and-falsy.html)
+- [Security model](https://liquidjs.com/tutorials/security-model.html)
+- [Differences from Shopify Liquid](https://liquidjs.com/tutorials/differences.html)
+- [Migrate to v9](https://liquidjs.com/tutorials/migrate-to-9.html)
+- [Changelog](https://liquidjs.com/tutorials/changelog.html)
+
+## Reference
+
+- [Tags](https://liquidjs.com/tags/overview.html)
+- [Filters](https://liquidjs.com/filters/overview.html)
+- [API (TypeDoc)](https://liquidjs.com/api/)
+- [Playground](https://liquidjs.com/playground.html)

docs/source/manifest.json

@@ -1,7 +1,7 @@
 {
   "short_name": "LiquidJS",
   "name": "LiquidJS",
-  "description": "A simple, expressive and safe Shopify / GitHub Pages compatible template engine in pure JavaScript.",
+  "description": "A simple, expressive, extensible Liquid template engine for JavaScript",
   "icons": [
     {
       "src": "/icon/apple-touch-icon-57x57.png",

docs/source/tags/assign.md

@@ -1,5 +1,5 @@
 ---
-title: Assign
+title: assign
 ---
 
 {% since %}v1.9.1{% endsince %}

docs/source/tags/case.md

@@ -4,7 +4,7 @@ title: case
 
 {% since %}v1.9.1{% endsince %}
 
-Creates a switch statement to compare a variable with different values. `case` initializes the switch statement, and `when` compares its values.
+Creates a switch statement to compare a variable with different values. `case` initializes the switch statement, and `when` tags compare values.
 
 Input
 ```liquid

docs/source/tags/comment.md

@@ -1,5 +1,5 @@
 ---
-title: Comment
+title: comment
 ---
 
 {% since %}v1.9.1{% endsince %}

docs/source/tags/decrement.md

@@ -1,5 +1,5 @@
 ---
-title: Decrement
+title: decrement
 ---
 
 {% since %}v1.9.1{% endsince %}

docs/source/tags/echo.md

@@ -1,5 +1,5 @@
 ---
-title: Echo
+title: echo
 ---
 
 {% since %}v9.31.0{% endsince %}

docs/source/tags/for.md

@@ -1,5 +1,5 @@
 ---
-title: For
+title: for
 ---
 
 {% since %}v1.9.1{% endsince %}

docs/source/tags/if.md

@@ -1,5 +1,5 @@
 ---
-title: If
+title: if
 ---
 
 {% since %}v1.9.1{% endsince %}

docs/source/tags/include.md

@@ -1,5 +1,5 @@
 ---
-title: Include
+title: include
 ---
 
 {% since %}v1.9.1{% endsince %}
@@ -22,11 +22,11 @@ If [extname][extname] option is set, the above `.liquid` extension becomes optio
 {% include 'footer' %}
 ```
 
-When a partial template is rendered by `include`, the code inside it can access its parent's variables but its parent cannot access variables defined inside a included template.
+When a partial template is rendered by `include`, the code inside it can access its parent's variables but its parent cannot access variables defined inside an included template.
 
 ## Passing Variables
 
-Variables defined in parent's scope can be passed to a the partial template by listing them as parameters on the `include` tag:
+Variables defined in the parent's scope can be passed to the partial template by listing them as parameters on the `include` tag:
 
 ```liquid
 {% assign my_variable = 'apples' %}
@@ -70,11 +70,11 @@ This way, you don't need to escape `"` in the filename expression.
 {% include prefix/{{name | append: ".html"}} %}
 ```
 
-## Jekyll include
+## Jekyll `include`
 
 {% since %}v9.33.0{% endsince %}
 
-[jekyllInclude][jekyllInclude] is used to enable Jekyll-like include syntax. Defaults to `false`, when set to `true`:
+[jekyllInclude][jekyllInclude] is used to enable Jekyll-like `include` syntax. Defaults to `false`, when set to `true`:
 
 - Filename will be static: `dynamicPartials` now defaults to `false` (instead of `true`). And you can set `dynamicPartials` back to `true`.
 - Use `=` instead of `:` to separate parameter key-values.
@@ -86,7 +86,7 @@ For example, the following template:
 {% include article.html header="HEADER" content="CONTENT" %}
 ```
 
-`article.html` with following content:
+`article.html` with the following content:
 
 ```liquid
 <article>
@@ -95,7 +95,7 @@ For example, the following template:
 </article>
 ```
 
-Note that we're referencing the first parameter by `include.header` instead of `header`. Will output following:
+Note that we're referencing the first parameter by `include.header` instead of `header`. It will output the following:
 
 ```html
 <article>

docs/source/tags/increment.md

@@ -1,5 +1,5 @@
 ---
-title: Increment
+title: increment
 ---
 
 {% since %}v1.9.1{% endsince %}

docs/source/tags/layout.md

@@ -1,5 +1,5 @@
 ---
-title: Layout
+title: layout
 ---
 
 {% since %}v1.9.1{% endsince %}
@@ -31,12 +31,12 @@ If [extname][extname] option is set, the `.liquid` extension becomes optional:
 ```
 
 {% note info Scoping %}
-When a partial template is rendered by <code>layout</code>, its template have access for its caller's variables but not vice versa. Variables defined in layout will be popped out before control returning to its caller.
+When a partial template is rendered by the `layout` tag, its template has access to its caller's variables but not vice versa. Variables defined in `layout` will be popped out before control returns to its caller.
 {% endnote %}
 
 ## Multiple Blocks
 
-The layout file can contain multiple blocks, each with a specified name. The following snippets yield same result as in the above example.
+The `layout` file can contain multiple blocks, each with a specified name. The following snippets yield same result as in the above example.
 
 ```liquid
 // default-layout.liquid
@@ -53,7 +53,7 @@ The layout file can contain multiple blocks, each with a specified name. The fol
 
 ## Default Block Contents
 
-In the above layout files, blocks has empty contents. But it's not necessarily be empty, in which case, the block contents in layout files will be used as default templates. The following snippets are also equivalent to the above examples:
+In the above `layout` files, blocks have empty contents. They do not necessarily need to be empty; in that case, the block contents in `layout` files will be used as default templates. The following snippets are also equivalent to the above examples:
 
 ```liquid
 // default-layout.liquid
@@ -68,7 +68,7 @@ In the above layout files, blocks has empty contents. But it's not necessarily b
 
 ## Passing Variables
 
-Variables defined in current template can be passed to a the layout template by listing them as parameters on the `layout` tag:
+Variables defined in the current template can be passed to the `layout` template by listing them as parameters on the `layout` tag:
 
 ```liquid
 {% assign my_variable = 'apples' %}

docs/source/tags/liquid.md

@@ -1,5 +1,5 @@
 ---
-title: Liquid
+title: liquid
 ---
 
 {% since %}v9.31.0{% endsince %}

docs/source/tags/overview.md

@@ -5,14 +5,14 @@ description: Description and demo for each Liquid tag
 
 LiquidJS implements business-logic independent tags that are typically implemented in [shopify/liquid][shopify/liquid]. This section contains the specification and demos for all the tags implemented by LiquidJS.
 
-There're a dozen of tags supported by LiquidJS, with all tags in [shopify/liquid][shopify/liquid]. These tags can be categorized into these groups:
+There are a dozen tags supported by LiquidJS, including all tags in [shopify/liquid][shopify/liquid]. These tags can be categorized into these groups:
 
 Category | Purpose | Tags
 --- | --- | ---
-Iteration | iterate over a collection | for, cycle, tablerow
-Control Flow | control the execution branch of template rendering | if, unless, elsif, else, case, when
-Variable | define and alter variables | assign, increment, decrement, capture, echo
-File | include another template or extend a layout template | render, include, layout
-Language | temporarily disable LiquidJS syntax | # (inline comment), raw, comment, liquid
+Iteration | iterate over a collection | `for`, `cycle`, `tablerow`
+Control Flow | control the execution branch of template rendering | `if`, `unless`, `elsif`, `else`, `case`, `when`
+Variable | define and alter variables | `assign`, `increment`, `decrement`, `capture`, `echo`
+File | include another template or extend a layout template | `render`, `include`, `layout`
+Language | temporarily disable LiquidJS syntax | `#`, `raw`, `comment`, `liquid`
 
 [shopify/liquid]: https://github.com/Shopify/liquid

docs/source/tags/raw.md

@@ -1,5 +1,5 @@
 ---
-title: Raw
+title: raw
 ---
 
 {% since %}v1.9.1{% endsince %}

docs/source/tags/render.md

@@ -1,5 +1,5 @@
 ---
-title: Render
+title: render
 ---
 
 {% since %}v9.2.0{% endsince %}
@@ -32,7 +32,7 @@ When a partial template is rendered, the code inside it can't access its parent'
 
 ## Passing Variables
 
-Variables defined in parent's scope can be passed to a the partial template by listing them as parameters on the render tag:
+Variables defined in the parent's scope can be passed to the partial template by listing them as parameters on the `render` tag:
 
 ```liquid
 {% assign my_variable = 'apples' %}

docs/source/tags/tablerow.md

@@ -1,5 +1,5 @@
 ---
-title: Table Row
+title: tablerow
 ---
 
 {% since %}v1.9.1{% endsince %}
@@ -88,7 +88,7 @@ Output
 
 ### limit
 
-Exits the tablerow after a specific index.
+Exits the `tablerow` after a specific index.
 
 ```liquid
 {% tablerow product in collection.products cols:2 limit:3 %}
@@ -98,7 +98,7 @@ Exits the tablerow after a specific index.
 
 ### offset
 
-Starts the tablerow after a specific index.
+Starts the `tablerow` after a specific index.
 
 ```liquid
 {% tablerow product in collection.products cols:2 offset:3 %}

docs/source/tags/unless.md

@@ -1,5 +1,5 @@
 ---
-title: Unless
+title: unless
 ---
 
 {% since %}v1.9.1{% endsince %}

docs/source/tutorials/access-scope-in-filters.md

@@ -2,7 +2,7 @@
 title: Access Scope in Filters
 ---
 
-As covered in [Register Filters/Tags][register-filters], we can access filter arguments directly in filter function like:
+As covered in [Register Filters/Tags][register-filters], we can access filter arguments directly in a filter function like:
 
 ```javascript
 // Usage: {{ 1 | add: 2, 3 }}
@@ -10,7 +10,7 @@ As covered in [Register Filters/Tags][register-filters], we can access filter ar
 engine.registerFilter('add', (initial, arg1, arg2) => initial + arg1 + arg2)
 ```
 
-When it comes to stateful filters, for example transform a URL path to full URL, we'll need to access a `origin` in current scope:
+When it comes to stateful filters, for example transforming a URL path to a full URL, we'll need to access an `origin` in the current scope:
 
 ```javascript
 // Usage: {{ '/index.html' | fullURL }}

docs/source/tutorials/caching.md

@@ -2,13 +2,13 @@
 title: Caching
 ---
 
-In a typical website project, we'll have a directory of view templates and they'll be rendered multiple times. In production environment the template files are not likely to be changed over time (other than re-deployments). Thus it makes sense to cache the file contents and the parsed templates (in a kind of AST) to improve performance.
+In a typical website project, we'll have a directory of view templates and they'll be rendered multiple times. In a production environment the template files are not likely to change over time (other than re-deployments). Thus it makes sense to cache the file contents and the parsed templates (in a kind of AST) to improve performance.
 
 LiquidJS provides multiple ways to cache the parsed templates to improve performance.
 
 ## Programmatically
 
-The [.parse()][parse], [.parseFile()][parseFile], [.parseFileSync()][parseFileSync] APIs are used to parse templates from string or files. The result template can be then rendered multiple times with different context.
+The [.parse()][parse], [.parseFile()][parseFile], [.parseFileSync()][parseFileSync] APIs are used to parse templates from strings or files. The resulting template can then be rendered multiple times with different context.
 
 Parse from string:
 

docs/source/tutorials/contribution-guidelines.md

@@ -16,11 +16,11 @@ Getting started and building is described in [CONTRIBUTING.md](https://github.co
 
 **Commit Message**: Please align to [the Angular Commit Message Guidelines](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#commits), especially note the [type identifier](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#type), on which semantic-release bot depends.
 
-**Backward-Compatibility**: please be backward-compatible. LiquidJS is used by multiple layers of softwares, including underlying libraries, compilers, site generators and Web servers. It's not easy to do a major upgrade for most of them.
+**Backward-Compatibility**: please be backward-compatible. LiquidJS is used by multiple layers of software, including underlying libraries, compilers, site generators and Web servers. It's not easy to do a major upgrade for most of them.
 
 ## Financial Support
 
-LiquidJS is Open Source and Free. To help it live and thrive, especially when LiquidJS is benefiting your business, please consider contribute on [GitHub Sponsors](https://github.com/sponsors/harttle) or [Open Collective][oc].
+LiquidJS is Open Source and Free. To help it live and thrive, especially when LiquidJS is benefiting your business, consider contributing on [GitHub Sponsors](https://github.com/sponsors/harttle) or [Open Collective][oc].
 
 I'll add all financial contributors into [README.md](https://github.com/harttle/liquidjs#financial-support) and it'll be also shown on https://liquidjs.com after next GitHub Actions build.
 

docs/source/tutorials/differences.md

@@ -4,7 +4,7 @@ title: Differences with Shopify/liquid
 
 ## Compatibility
 
-Being compatible with the Ruby version is one of our priorities. Liquid language is originally [implemented in Ruby][ruby-liquid] and used by Shopify and Jekyll (and thus GitHub Pages). As you can see it's one of the most popular template engines in Ruby. There're lots of people using LiquidJS to serve their templates originally written for Shopify themes and Jekyll sites.
+Being compatible with the Ruby version is one of our priorities. Liquid language is originally [implemented in Ruby][ruby-liquid] and used by Shopify and Jekyll (and thus GitHub Pages). As you can see it's one of the most popular template engines in Ruby. There are lots of people using LiquidJS to serve their templates originally written for Shopify themes and Jekyll sites.
 
 So "being compatible" means serving developers from Shopify and Jekyll well:
 
@@ -13,8 +13,8 @@ So "being compatible" means serving developers from Shopify and Jekyll well:
 
 In the meantime, it's now implemented in JavaScript, that means it has to be more powerful:
 
-* **Async as first-class citizen**. Filters and tags can be implemented asynchronously by return a `Promise`.
-* **Also can be sync**. For scenarios that are not I/O intensive, render synchronously can be much faster. You can call synchronous APIs like `.renderSync()` as long as all the filters and tags in template support to be rendered synchronously. All builtin filters/tags support both sync and async render.
+* **Async as a first-class citizen**. Filters and tags can be implemented asynchronously by returning a `Promise`.
+* **Can also be synchronous**. For scenarios that are not I/O intensive, rendering synchronously can be much faster. You can call synchronous APIs like `.renderSync()` as long as all the filters and tags in the template can be rendered synchronously. All built-in filters/tags support both sync and async render.
 * **[Abstract file system][afs]**. Along with async feature, LiquidJS can be used to serve templates stored in Databases [#414][#414], on remote HTTP server [#485][#485], and so on.
 * **Additional tags and filters** like `layout` and `json`, `inspect`, `where_exp`, `group_by`, etc., see below for details.
 

docs/source/tutorials/dos.md

@@ -1,57 +0,0 @@
----
-title: DoS Prevention
----
-
-When the template or data context cannot be trusted, enabling DoS prevention options is crucial. LiquidJS provides 3 options for this purpose: `parseLimit`, `renderLimit`, and `memoryLimit`.
-
-## TL;DR
-
-Setting these options can largely ensure that your LiquidJS instance won't hang for extended periods or consume excessive memory. These limits are based on the available JavaScript APIs, so they are not precise hard limits but thresholds to help prevent your process from failing or hanging.
-
-```typescript
-const liquid = new Liquid({
-    parseLimit: 1e8, // typical size of your templates in each render
-    renderLimit: 1000, // limit each render to be completed in 1s
-    memoryLimit: 1e9, // memory available for LiquidJS (1e9 for 1GB)
-})
-```
-
-When a `parse()` or `render()` cannot be completed within given resource, it throws.
-
-## parseLimit
-
-[parseLimit][parseLimit] restricts the size (character length) of templates parsed in each `.parse()` call, including referenced partials and layouts. Since LiquidJS parses template strings in near O(n) time, limiting total template length is usually sufficient.
-
-A typical PC handles `1e8` (100M) characters without issues.
-
-## renderLimit
-
-Restricting template size alone is insufficient because dynamic loops with large counts can occur in render time. [renderLimit][renderLimit] mitigates this by limiting the time consumed by each `render()` call.
-
-```liquid
-{%- for i in (1..10000000) -%}
-    order: {{i}}
-{%- endfor -%}
-```
-
-Render time is checked on a per-template basis (before rendering each template). In the above example, there are 2 templates in the loop: `order: ` and `{{i}}`, render time will be checked 10000000x2 times.
-
-For time-consuming tags and filters within a single template, the process can still hang. For fully controlled rendering, consider using a process manager like [paralleljs][paralleljs].
-
-## memoryLimit
-
-Even with small number of templates and iterations, memory usage can grow exponentially. In the following example, memory doubles with each iteration:
-
-```liquid
-{% assign array = "1,2,3" | split: "," %}
-{% for i in (1..32) %}
-    {% assign array = array | concat: array %}
-{% endfor %}
-```
-
-[memoryLimit][memoryLimit] restricts memory-sensitive filters to prevent excessive memory allocation. As [JavaScript uses GC to manage memory](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Memory_management), `memoryLimit` limits only the total number of objects allocated by memory sensitive filters in LiquidJS thus may not reflect the actual memory footprint.
-
-[paralleljs]: https://www.npmjs.com/package/paralleljs
-[parseLimit]: /api/interfaces/LiquidOptions.html#parseLimit
-[renderLimit]: /api/interfaces/LiquidOptions.html#renderLimit
-[memoryLimit]: /api/interfaces/LiquidOptions.html#memoryLimit

docs/source/tutorials/drops.md

@@ -95,7 +95,7 @@ engine.parseAndRender("{{color}}", context).then(html => console.log(html))
 
 ## toLiquid
 
-`toLiquid()` is not a method of `Drop`, but it can be used to return a `Drop`. In cases where you have a fixed structure in the `context` that cannot change its values, you can implement `toLiquid()` to let LiquidJS use the returned value instead of itself to render the templates.
+`toLiquid()` is not a method of `Drop`, but it can be used to return a `Drop`. In cases where you have a fixed structure in the `context` that cannot change its values, you can implement `toLiquid()` to let LiquidJS use the returned value instead of the object itself when rendering templates.
 
 ```javascript
 import { Liquid, Drop } from 'liquidjs'

docs/source/tutorials/escaping.md

@@ -2,10 +2,10 @@
 title: Escaping
 ---
 
-Escaping is important in all languages, including LiquidJS. While escaping has 2 different meanings for a template engine:
+Escaping is important in all languages, including LiquidJS. Escaping has two different meanings for a template engine:
 
 1. Escaping for the output, i.e. HTML escape. Used to escape HTML special characters so the output will not break HTML structures, aka HTML safe.
-2. Escaping for the language itself, i.e. Liquid escape. Used to output strings that's considered special in Liquid language. This will be useful when you're writing an article in Liquid template to introduce Liquid language.
+2. Escaping for the language itself, i.e. Liquid escape. Used to output strings that are considered special in the Liquid language. This is useful when you're writing an article in a Liquid template to introduce the Liquid language.
 
 ## HTML Escape
 
@@ -55,7 +55,7 @@ In LiquidJS, {{ this | escape }} will be HTML-escaped, but
 {{{ that }}} will not.
 ```
 
-Within strings literals in LiquidJS template, `\` can be used to escape special characters in string syntax. For example:
+Within string literals in a LiquidJS template, `\` can be used to escape special characters in string syntax. For example:
 
 Input
 ```liquid

docs/source/tutorials/intro-to-liquid.md

@@ -3,9 +3,9 @@ title: The Liquid Template Language
 describe: A short introduction to the Liquid template language and some simple demos.
 ---
 
-LiquidJS is a simple, expressive and safe [Shopify][shopify/liquid] / GitHub Pages compatible template engine in pure JavaScript. The purpose of this repo is to provide a standard Liquid implementation for the JavaScript community. Liquid is originally implemented in Ruby and used by GitHub Pages, Jekyll and Shopify, see [Differences with Shopify/liquid][diff].
+Liquid is a template language originally implemented in Ruby and used by Shopify, Jekyll, and GitHub Pages. LiquidJS implements it in JavaScript; see [Differences with Shopify/liquid][diff] for compatibility notes.
 
-LiquidJS syntax is relatively simple. There're 2 types of markups in LiquidJS:
+There are 2 types of markups in LiquidJS:
 
 - **Tags**. A tag consists of a tag name and optional arguments wrapped between `{%raw%}{%{%endraw%}` and `%}`.
 - **Outputs**. An output consists of a value and a list of filters, which is optional, wrapped between `{%raw%}{{{%endraw%}` and `}}`.
@@ -38,7 +38,7 @@ A complete list of filters supported by LiquidJS can be found [here](../filters/
 
 ## Tags
 
-**Tags** are used to control the template rendering process, manipulating template variables, inter-op with other templates, etc. For example `assign` can be used to define a variable which can be later used in the template:
+**Tags** are used to control the template rendering process, manipulating template variables, interacting with other templates, etc. For example `assign` can be used to define a variable that can be later used in the template:
 
 ```liquid
 {% assign foo = "FOO" %}
@@ -50,11 +50,10 @@ Typically tags appear in pairs with a start tag and a corresponding end tag. For
 {% if foo == "FOO" %}
     Variable `foo` equals "FOO"
 {% else %}
-    Variable `foo` not equals "FOO"
+    Variable `foo` does not equal "FOO"
 {% endif %}
 ```
 
 A complete list of tags supported by LiquidJS can be found [here](../tags/overview.html).
 
-[shopify/liquid]: https://github.com/Shopify/liquid
 [diff]: ./differences.html

docs/source/tutorials/migrate-to-9.md

@@ -2,7 +2,7 @@
 title: Migrate to LiquidJS 9
 ---
 
-LiquidJS 9 has some fundamental improvements, including bugfixes, new features and performance improvement due to higher target(see #137). There're also some breaking changes.
+LiquidJS 9 has some fundamental improvements, including bugfixes, new features and performance improvements due to a higher target (see #137). There are also some breaking changes.
 
 ## Features
 
@@ -14,11 +14,11 @@ LiquidJS 9 has some fundamental improvements, including bugfixes, new features a
 * Rewrite boolean expression evaluation order, [#130](https://github.com/harttle/liquidjs/issues/130);
 * `break` and `continue` tags omitting output before them, [#123](https://github.com/harttle/liquidjs/issues/123);
 * Fixes errors in React.js demo during yarn install, [#145](https://github.com/harttle/liquidjs/issues/145);
-* Promise typed Drops are not await-ed some times.
+* Promise typed Drops are not always awaited.
 
 ## Performance
 
-* Performance Improvements due to targeting to Node.js 8, see [#137](https://github.com/harttle/liquidjs/issues/137);
+* Performance Improvements due to targeting Node.js 8, see [#137](https://github.com/harttle/liquidjs/issues/137);
 * Memory footprint is reduced by 57.5%, see [#202](https://github.com/harttle/liquidjs/pull/202);
 * Render performance is improved by 100.3%, see [#205](https://github.com/harttle/liquidjs/pull/205).
 

docs/source/tutorials/operators.md

@@ -2,14 +2,14 @@
 title: Operators
 ---
 
-LiquidJS operators are very simple and different. There're 2 types of operators supported:
+LiquidJS operators are very simple and different. There are 2 types of operators supported:
 
 * Comparison operators: `==`, `!=`, `>`, `<`, `>=`, `<=`
-* Logic operators: `not`, `or`, `and`, `contains`
+* Logical operators: `not`, `or`, `and`, `contains`
 
-Thus numerical operators are not supported and you cannot even plus two numbers like this `{% raw %}{{a + b}}{% endraw %}`, instead we need a filter `{% raw %}{{ a | plus: b}}{% endraw %}`. Actually `+` is a valid variable name in LiquidJS.
+Thus arithmetic operators are not supported and you cannot add two numbers like this `{% raw %}{{a + b}}{% endraw %}`. Instead, use a filter: `{% raw %}{{ a | plus: b}}{% endraw %}`. Actually `+` is a valid variable name in LiquidJS.
 
-## Logic Operators
+## Logical Operators
 
 ### not
 
@@ -59,10 +59,10 @@ Input
 
 1. Comparison operators, and `contains`. All comparison operators alongside `contains` have the same (highest) precedence.
 2. `not` operator. It has slightly more precedence than `or` and `and`.
-3. `or` and `and` operators. These logic operators have the same (lowest) precedence.
+3. `or` and `and` operators. These logical operators have the same (lowest) precedence.
 
 ## Associativity
 
-Logic operators are evaluated from right to left, see [shopify docs][operator-order].
+Logical operators are evaluated from right to left, see [shopify docs][operator-order].
 
 [operator-order]: https://shopify.dev/docs/api/liquid/basics#order-of-operations

docs/source/tutorials/options.md

@@ -11,27 +11,27 @@ const engine = new Liquid({
 })
 ```
 
-{% note info API Document %}
-Following is an overview for all the options, for exact types and signatures please refer to <a href="https://liquidjs.com/api/interfaces/LiquidOptions.html" target="_self">LiquidOptions | API</a>.
+{% note info API documentation %}
+Following is an overview for all the options. For exact types and signatures, see <a href="https://liquidjs.com/api/interfaces/LiquidOptions.html" target="_self">LiquidOptions | API</a>.
 {% endnote %}
 
 ## cache
 
-**cache** is used to improve performance by caching previously parsed template structures, specially in cases when we're repeatedly parse or render files.
+**cache** is used to improve performance by caching previously parsed template structures, especially in cases when we repeatedly parse or render files.
 
-It's default to `false`. When setting to `true` a default LRU cache of size 1024 will be enabled. And certainly it can be a number which indicates the size of cache you want.
+It defaults to `false`. When set to `true`, a default LRU cache of size 1024 will be enabled. It can also be a number indicating the cache size you want.
 
 Additionally, it can also be a custom cache implementation. See [Caching][caching] for details.
 
 ## Partials/Layouts
 
-**root** is used to specify template directories for LiquidJS to lookup and read template files. Can be a single string and an array of strings. See [Render Files][render-file] for details.
+**root** is used to specify template directories for LiquidJS to look up and read template files. Can be a single string or an array of strings. See [Render Files][render-file] for details.
 
-**layouts** is used to specify template directories for LiquidJS to lookup files for `{% layout %}`. Same format as `root` and will default to `root` if not specified.
+**layouts** is used to specify template directories for LiquidJS to look up files for `{% layout %}`. Same format as `root` and will default to `root` if not specified.
 
-**partials** is used to specify template directories for LiquidJS to lookup files for `{% render %}` and `{% include %}`. Same format as `root` and will default to `root` if not specified.
+**partials** is used to specify template directories for LiquidJS to look up files for `{% render %}` and `{% include %}`. Same format as `root` and will default to `root` if not specified.
 
-**relativeReference** is set to `true` by default to allow relative filenames. Note that relatively referenced files are also need to be within corresponding root. For example you can reference another file like `{% render ../foo/bar %}` as long as `../foo/bar` is also within `partials` directory.
+**relativeReference** is set to `true` by default to allow relative filenames. Note that relatively referenced files also need to be within the corresponding root. For example you can reference another file like `{% render ../foo/bar %}` as long as `../foo/bar` is also within `partials` directory.
 
 ## dynamicPartials
 
@@ -62,7 +62,7 @@ LiquidJS defaults this option to <code>true</code> to be compatible with shopify
 - Use `=` instead of `:` to separate parameter key-values.
 - Parameters are under `include` variable instead of current scope.
 
-For example in the following template, `name.html` is not quoted, `header` and `"HEADER"` are separated by `=`, and the `header` parameter is referenced by `include.header`. More details please check out [include][include].
+For example in the following template, `name.html` is not quoted, `header` and `"HEADER"` are separated by `=`, and the `header` parameter is referenced by `include.header`. For more details, see [include][include].
 
 ```liquid
 // entry template
@@ -90,7 +90,7 @@ Before 2.0.1, <code>extname</code> is set to `.liquid` by default. To change tha
 
 ## fs
 
-**fs** is used to define a custom file system implementation which will be used by LiquidJS to lookup and read template files. See [Abstract File System][abstract-fs] for details.
+**fs** is used to define a custom file system implementation which will be used by LiquidJS to look up and read template files. See [Abstract File System][abstract-fs] for details.
 
 ## globals
 
@@ -98,9 +98,9 @@ Before 2.0.1, <code>extname</code> is set to `.liquid` by default. To change tha
 
 ## jsTruthy
 
-**jsTruthy** is used to use standard JavaScript truthiness rather than the Shopify.
+**jsTruthy** is used to use standard JavaScript truthiness rather than Shopify's.
 
-it defaults to false.  For example, when set to true, a blank string would evaluate to false with jsTruthy. With Shopify's truthiness, a blank string is true.
+It defaults to `false`. For example, when set to `true`, a blank string would evaluate to false with jsTruthy. With Shopify's truthiness, a blank string is true.
 
 ## outputEscape
 
@@ -108,13 +108,13 @@ it defaults to false.  For example, when set to true, a blank string would evalu
 
 - For untrusted output variables, set `outputEscape: "escape"` makes them be HTML escaped by default. You'll need [raw][raw] filter for direct output.
 - `"json"` is useful when you're using LiquidJS to create valid JSON files.
-- It can even be a function which allows you to control what variables are output throughout LiquidJS. Please note the input can be any type other than string, e.g. an filter returned an non-string value.
+- It can even be a function that allows you to control what variables are output throughout LiquidJS. Please note the input can be any type other than string, e.g. a filter may return a non-string value.
 
 ## Date
 
 **timezoneOffset** is used to specify a different timezone to output dates, your local timezone will be used if not specified. For example, set `timezoneOffset: 0` to output all dates in UTC/GMT 00:00.
 
-**preserveTimezones** is a boolean effects only literal timestamps. When set to `true`, all literal timestamps will remain the same when output. This is a parser option, so Date objects passed to LiquidJS as data will not be affected. Note that `preserveTimezones` has a higher priority than `timezoneOffset`.
+**preserveTimezones** is a boolean that affects only literal timestamps. When set to `true`, all literal timestamps will remain the same when output. This is a parser option, so Date objects passed to LiquidJS as data will not be affected. Note that `preserveTimezones` has a higher priority than `timezoneOffset`.
 
 **dateFormat** is used to specify a default format to output dates. `%A, %B %-e, %Y at %-l:%M %P %z` will be used if not specified. For example, set `dateFormat: %Y-%m-%dT%H:%M:%S:%LZ` to output all dates in [JavaScript Date.toJson()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toJSON) format.
 

docs/source/tutorials/parse-parameters.md

@@ -4,7 +4,7 @@ title: Parse Parameters
 
 ## Access Raw Parameters
 
-As covered in [Register Filters/Tags][register-tags], tag parameters is available on `tagToken.args` as a raw string. For example:
+As covered in [Register Filters/Tags][register-tags], tag parameters are available on `tagToken.args` as a raw string. For example:
 
 ```javascript
 // Usage: {% random foo bar coo %}
@@ -66,7 +66,7 @@ Async calls in LiquidJS are implemented by generators directly, for we can call
 
 ## Parse Key-Value Pairs as Named Parameters
 
-Named parameters become very handy when there're optional parameters or lots of parameters, in which case the order of parameters is not important. This is exactly what [Hash][Hash] class is invented for.
+Named parameters become very handy when there are optional parameters or lots of parameters, in which case the order of parameters is not important. This is exactly what the [Hash][Hash] class was invented for.
 
 ```liquid
 {% random from:2, to:max %}

docs/source/tutorials/partials-and-layouts.md

@@ -25,7 +25,7 @@ color: 'red' shape: 'circle'
 color: 'yellow' shape: 'square'
 ```
 
-More details please refer to the [render](../tags/render.html) tag.
+For more details, see the [render](../tags/render.html) tag.
 
 {% note tip The ".liquid" Extension %}
 The ".liquid" extension in <code>layout</code>, <code>render</code> and <code>include</code> can be omitted if Liquid instance is created using `extname: ".liquid"` option. See <a href="./options.html#extname">the extname option</a> for details.
@@ -54,4 +54,4 @@ My page content
 Footer
 ```
 
-More details please refer to the [layout](../tags/layout.html) tag.
+For more details, see the [layout](../tags/layout.html) tag.

docs/source/tutorials/plugins.md

@@ -6,9 +6,9 @@ A number of tags and filters can be encapsulated into a **plugin**, which will b
 
 ## Write a Plugin
 
-A liquidjs plugin is simple function which takes the [Liquid class][liquid] as the first parameter and the Liquid instance for `this`. We can call liquidjs APIs on `this` to make certain changes, especially [register filters and tags][register].
+A LiquidJS plugin is a simple function that takes the [Liquid class][liquid] as the first parameter and uses the Liquid instance for `this`. We can call LiquidJS APIs on `this` to make certain changes, especially [register filters and tags][register].
 
-Now we'll make a plugin to upper case every letter of the input, save the following snippet to `upup.js`:
+Now we'll make a plugin to uppercase every letter of the input. Save the following snippet to `upup.js`:
 
 ```javascript
 /**

docs/source/tutorials/register-filters-tags.md

@@ -62,7 +62,23 @@ See existing filter implementations here: <https://github.com/harttle/liquidjs/t
 
 ## Unregister Tags/Filters
 
-In some cases it's desirable to disable some tags/filters (see [#324](https://github.com/harttle/liquidjs/issues/324)), you'll need to register a dummy tag/filter in which an corresponding Error throws.
+Filters can be unregistered by name:
+
+```javascript
+engine.unregisterFilter('plus')
+```
+
+With [`strictFilters`][strict-filters] enabled, using an unregistered filter will throw an error. Otherwise, the filter will be skipped.
+
+Built-in filters can be registered again using the exported `filters` object:
+
+```javascript
+import { filters } from 'liquidjs'
+
+engine.registerFilter('plus', filters.plus)
+```
+
+To disable a tag, or to make a disabled filter throw regardless of `strictFilters`, register a dummy implementation that throws a corresponding error (see [#324](https://github.com/harttle/liquidjs/issues/324)):
 
 ```javascript
 // disable a tag
@@ -81,3 +97,5 @@ function disabledFilter(name) {
 }
 engine.registerFilter('plus', disabledFilter('plus'));
 ```
+
+[strict-filters]: /tutorials/options.html#strict

docs/source/tutorials/render-file.md

@@ -38,7 +38,7 @@ name: alice
 
 ## Template Lookup
 
-Template files names passed to [renderFile][renderFile], [parseFile][parseFile], [renderFileSync][renderFileSync], [parseFileSync][parseFileSync] APIs,
+Template file names passed to [renderFile][renderFile], [parseFile][parseFile], [renderFileSync][renderFileSync], [parseFileSync][parseFileSync] APIs,
 and [include][include], [layout][layout] tags are resolved against [the root option][root].
 
 It can be a string-typed path (see above example), or a list of root directories, in which case templates will be looked up in that order. e.g.
@@ -96,7 +96,7 @@ var engine = new Liquid({
 
 ## In-memory Template
 
-To facilitate rendering w/o files, there's a `templates` option to specify a mapping of filenames and their content. LiquidJS will read templates from the mapping.
+To facilitate rendering without files, there's a `templates` option to specify a mapping of filenames and their content. LiquidJS will read templates from the mapping.
 
 ```typescript
 const engine = new Liquid({

docs/source/tutorials/render-tag-content.md

@@ -2,7 +2,7 @@
 title: Render Tag Content
 ---
 
-Custom tags can have content template and can be nested. This article describes how to implement custom tags that consists of a *begin tag*, an *end tag*, and template content between them.
+Custom tags can have content templates and can be nested. This article describes how to implement custom tags that consist of a *begin tag*, an *end tag*, and template content between them.
 
 ## Render Tag Content
 
@@ -22,12 +22,12 @@ Expected output:
 </div>
 ```
 
-Firstly, [register][register-tags] a tag with name `wrap` and parse the content into `this.tpls`. Here in `parse(tagToken, remainTokens)`,
+Firstly, [register][register-tags] a tag named `wrap` and parse the content into `this.tpls`. Here in `parse(tagToken, remainTokens)`:
 
 - `tagToken` is current token `{%raw%}{% wrap %}{%endraw%}`, and
 - `remainTokens` is an array of all tokens following `{%raw%}{% wrap %}{%endraw%}` until the end of this template file.
 
-Basically, what we need to do is take/`.shift()` enough tags from `remainTokens` until we got a `endwrap` token (the name can be arbitrary, but in convention, we need it to be `endwrap`). And if there's no `endwrap` until the end of template file, we need to throw an tag-not-closed `Error`.
+Basically, what we need to do is take/`.shift()` enough tags from `remainTokens` until we get an `endwrap` token (the name can be arbitrary, but by convention it should be `endwrap`). And if there's no `endwrap` until the end of the template file, we need to throw a tag-not-closed `Error`.
 
 ```javascript
 engine.registerTag('wrap', {
@@ -57,11 +57,11 @@ engine.registerTag('wrap', {
 })
 ```
 
-`.renderTemplates()` can be async, we need `yield` to wait it complete. More details on async in LiquidJS, please refer to [Sync and Async][async]. Other parts of `render()` method is quite straightforward. Here's a JSFiddle version: <https://jsfiddle.net/por0zcn1/3/>
+`.renderTemplates()` can be async; we need `yield` to wait for it to complete. For more details on async in LiquidJS, see [Sync and Async][async]. Other parts of the `render()` method are quite straightforward. Here's a JSFiddle version: <https://jsfiddle.net/por0zcn1/3/>
 
 ## Using ParseStream
 
-When it comes to complex tags like [for][for] and [if][if], the `parse()` can be very complicated. There's a [ParseStream][ParseStream] utility to organize the `parse()` in event-based style. Following is a re-written `parse()` using `ParseStream` and does exactly the same as above example.
+When it comes to complex tags like [for][for] and [if][if], the `parse()` can be very complicated. There's a [ParseStream][ParseStream] utility to organize the `parse()` in event-based style. Following is a re-written `parse()` using `ParseStream` that does exactly the same as the example above.
 
 ```javascript
 parse(tagToken, remainTokens) {
@@ -79,7 +79,7 @@ Here's a JSFiddle version: <https://jsfiddle.net/por0zcn1/4/>. For simplicity, t
 
 ## Manipulate the Context
 
-The `wrap` tag above doesn't seem to be very useful, without using that tag we can render the content anyway. Now we're going to implement a `repeat` tag to render the content 2 times (we can also add a [parameter][parameter] to render arbitrary times).
+The `wrap` tag above doesn't seem very useful; even without using that tag, we can render the content anyway. Now we're going to implement a `repeat` tag to render the content 2 times (we can also add a [parameter][parameter] to render an arbitrary number of times).
 
 ```liquid
 {% repeat %}

docs/source/tutorials/security-model.md

@@ -0,0 +1,89 @@
+---
+title: Security Model
+---
+
+LiquidJS provides DoS-oriented limits (`parseLimit`, `renderLimit`, `memoryLimit`) to reduce risk. This page summarizes those limits, [`ownPropertyOnly`][ownPropertyOnly], custom [`Drop`][drop] usage, and the security boundary to assume in production.
+
+## Security boundary
+
+The built-in limits are cooperative safeguards, not strict runtime isolation.
+
+- They do **not** equal process RSS/heap usage.
+- They do **not** sandbox JavaScript execution.
+- They should be combined with process/container limits and request timeouts for defense in depth.
+
+## Limits at a glance
+
+- [parseLimit][parseLimit]: limit total template size per `parse()` call.
+- [renderLimit][renderLimit]: limit total render time per `render()` call.
+- [memoryLimit][memoryLimit]: cooperatively limit memory-sensitive allocations counted by LiquidJS.
+
+## Limit details
+
+### parseLimit
+
+[parseLimit][parseLimit] restricts the size (character length) of templates parsed in each `.parse()` call, including referenced partials and layouts. Since LiquidJS parses template strings in near O(n) time, limiting total template length is usually sufficient.
+
+A typical PC handles `1e8` (100M) characters without issues.
+
+### renderLimit
+
+Restricting template size alone is insufficient because dynamic loops with large counts can occur during rendering. [renderLimit][renderLimit] mitigates this by limiting the time consumed by each `render()` call.
+
+```liquid
+{%- for i in (1..10000000) -%}
+    order: {{i}}
+{%- endfor -%}
+```
+
+Render time is checked on a per-template basis (before rendering each template). In the above example, there are 2 templates in the loop: `order: ` and `{{i}}`, render time will be checked 10000000x2 times.
+
+`renderLimit` is not a hard CPU limiter. It is checked between template renders, so compute-intensive filters/tags/user-defined functions or deeply nested template execution between checks can still cause DoS.
+
+### memoryLimit
+
+`memoryLimit` only limits operations that LiquidJS explicitly counts.
+
+- Counted: memory-sensitive LiquidJS operations that call internal memory accounting.
+- Not guaranteed counted: arbitrary user object behavior such as custom `toValue()`/`toString()` chains, or other host-side code that allocates outside LiquidJS accounting points.
+
+In other words, `memoryLimit` limits what LiquidJS counts, not every byte your process may allocate.
+
+Even with a small number of templates and iterations, memory usage can grow exponentially. In the following example, memory doubles with each iteration:
+
+```liquid
+{% assign array = "1,2,3" | split: "," %}
+{% for i in (1..32) %}
+    {% assign array = array | concat: array %}
+{% endfor %}
+```
+
+As [JavaScript uses GC to manage memory](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Memory_management), `memoryLimit` may not reflect the actual memory footprint.
+
+## `ownPropertyOnly` and scope data
+
+With [`ownPropertyOnly`][ownPropertyOnly] `true`, plain scope objects only expose **own** properties (no inherited / `Object.prototype` keys). Default `false` follows normal JS property access. Use `true` for untrusted or polluted objects; add [`strictVariables`][strictVariables] if missing paths should error. Override per render via [`RenderOptions`][renderOwnPropertyOnly]. This is a read policy for scope data—not a sandbox for filters, tags, or your code.
+
+## Custom `Drop` classes
+
+[`Drop`][drop] values are not restricted the same way: LiquidJS still reads the prototype chain and may call [`liquidMethodMissing`][liquidMethodMissing]. **You** control what a drop exposes; narrow APIs and never feed unsafe data into drops unless the class is built for template access. `ownPropertyOnly` alone does not harden custom drops—audit them like any privileged code.
+
+## Online service guidance
+
+If you run an online service, avoid rendering fully user-defined templates whenever possible.
+
+- Prefer curated templates or a restricted template subset.
+- If user-defined templates are required, isolate rendering (worker/process/container), enforce OS/container memory and CPU limits, and apply request rate limits.
+- Treat `parseLimit`/`renderLimit`/`memoryLimit` as one layer in a broader DoS defense strategy.
+
+For heavy single-template operations, process-level isolation is still recommended (for example with [paralleljs][paralleljs]).
+
+[paralleljs]: https://www.npmjs.com/package/paralleljs
+[parseLimit]: /api/interfaces/LiquidOptions.html#parseLimit
+[renderLimit]: /api/interfaces/LiquidOptions.html#renderLimit
+[memoryLimit]: /api/interfaces/LiquidOptions.html#memoryLimit
+[ownPropertyOnly]: /api/interfaces/LiquidOptions.html#ownPropertyOnly
+[renderOwnPropertyOnly]: /api/interfaces/RenderOptions.html#ownPropertyOnly
+[strictVariables]: /api/interfaces/LiquidOptions.html#strictVariables
+[drop]: /api/classes/Drop.html
+[liquidMethodMissing]: /api/classes/Drop.html#liquidMethodMissing

docs/source/tutorials/setup.md

@@ -47,7 +47,7 @@ Pre-built UMD bundles are also available:
 <script src="https://cdn.jsdelivr.net/npm/liquidjs/dist/liquid.browser.umd.js"></script>
 ```
 
-{% note info Working Demo %} Here's a living demo on jsFiddle: <a href="https://jsfiddle.net/pd4jhzLs/1/" target="_blank">jsfiddle.net/pd4jhzLs/1/</a>, and the source code is also available in <a href="https://github.com/harttle/liquidjs/blob/master/demo/browser/" target="_blank">liquidjs/demo/browser/</a>.{% endnote %}
+{% note info Working Demo %} Here's a live demo on jsFiddle: <a href="https://jsfiddle.net/pd4jhzLs/1/" target="_blank">jsfiddle.net/pd4jhzLs/1/</a>, and the source code is also available in <a href="https://github.com/harttle/liquidjs/blob/master/demo/browser/" target="_blank">liquidjs/demo/browser/</a>.{% endnote %}
 
 {% note warn Compatibility %} You may need a <a href="https://github.com/taylorhakes/promise-polyfill" target="_blank">Promise polyfill</a> for legacy browsers like IE and Android UC, see <a href="https://caniuse.com/#feat=promises" target="_blank">caniuse statistics</a>. {% endnote %}
 

docs/source/tutorials/static-analysis.md

@@ -5,7 +5,7 @@ title: Static Template Analysis
 {% since %}v10.20.0{% endsince %}
 
 {% note warn Experimental %}  
-Note that this is an experimental feature and future APIs are subject to change. And internal structures returned can be changed w/o a major version bump.
+Note that this is an experimental feature and future APIs are subject to change. Internal structures returned can be changed without a major version bump.
 {% endnote %}
 
 {% note info Sync and Async %}
@@ -234,9 +234,9 @@ This is an example of an object returned from `Liquid.analyze()`, passing it the
 
 ### Analyzing Custom Tags
 
-For static analysis to include results from custom tags, those tags must implement some additional methods defined on the [Template interface]( /api/interfaces/Template.html). LiquidJS will use the information returned from these methods to traverse the template and report variable usage.
+For static analysis to include results from custom tags, those tags must implement some additional methods defined on the [Template interface](/api/interfaces/Template.html). LiquidJS will use the information returned from these methods to traverse the template and report variable usage.
 
-Not all methods are required, depending in the kind of tag. If it's a block with a start tag, end tag and any amount of Liquid markup in between, it will need to implement the [`children()`](/api/interfaces/Template.html#children) method. `children()` is defined as a generator, so that we can use it in synchronous and asynchronous contexts, just like `render()`. It should return HTML content, output statements and tags that are child nodes of the current tag.
+Not all methods are required, depending on the kind of tag. If it's a block with a start tag, end tag and any amount of Liquid markup in between, it will need to implement the [`children()`](/api/interfaces/Template.html#children) method. `children()` is defined as a generator, so that we can use it in synchronous and asynchronous contexts, just like `render()`. It should return HTML content, output statements and tags that are child nodes of the current tag.
 
 The [`blockScope()`](/api/interfaces/Template.html#blockScope) method is responsible for telling LiquidJS which names will be in scope for the duration of the tag's block. Some of these names could depend on the tag's arguments, and some will be fixed, like `forloop` from the `{% for %}` tag.
 

docs/source/tutorials/sync-and-async.md

@@ -2,11 +2,11 @@
 title: Sync and Async
 ---
 
-LiquidJS supports both sync and async evaluate, and can be used with Promises. To reuse the same set of tag/filter implementations in both sync and async, LiquidJS tags are implemented as generators.
+LiquidJS supports both synchronous and asynchronous evaluation, and can be used with Promises. To reuse the same set of tag/filter implementations in both sync and async modes, LiquidJS tags are implemented as generators.
 
 ## Sync and Async API
 
-All major methods on [Liquid][Liquid] supports both sync and async. These methods return Promises:
+All major methods on [Liquid][Liquid] support both sync and async. These methods return Promises:
 
 - `render()`
 - `renderFile()`
@@ -44,11 +44,11 @@ engine.registerTag('upper', class UpperTag extends Tag {
 })
 ```
 
-All builtin tags are implemented this way and safe to use in both sync and async (I'll call it *sync-compatible*). To make your custom tag *sync-compatible*, you'll need to:
+All built-in tags are implemented this way and are safe to use in both sync and async modes (I'll call it *sync-compatible*). To make your custom tag *sync-compatible*, you'll need to:
 
 - declare render function as `* render()`, in which
 - do not directly `return <Promise>`, and
-- do not call any APIs that returns a Promise.
+- do not call any APIs that return a Promise.
 
 ## Call APIs that return a Promise
 
@@ -92,7 +92,7 @@ engine.registerTag('upper', class UpperTag extends Tag {
 
 ## Async only Tags
 
-If your tag is intend to be used only asynchronously, it can be declared as `async render()` so you can use `await` in its implementation directly:
+If your tag is intended to be used only asynchronously, it can be declared as `async render()` so you can use `await` in its implementation directly:
 
 ```typescript
 import { toPromise, TagToken, Context, Emitter, TopLevelToken, Value, Tag, Liquid } from 'liquidjs'

docs/source/tutorials/truthy-and-falsy.md

@@ -2,7 +2,7 @@
 title: Truthy and Falsy
 ---
 
-Though [Liquid][sl] is platform-independent, there're [certain differences][diff] with [the Ruby version][ruby], one of which is the `truthy` value.
+Though [Liquid][sl] is platform-independent, there are [certain differences][diff] with [the Ruby version][ruby], one of which is the `truthy` value.
 
 ## The Truth Table
 
@@ -24,7 +24,7 @@ value          | truthy | falsy
 
 ## Use JavaScript Truthy
 
-Note that liquidjs use Shopify's truthiness by default. But it can be toggled to used standard JavaScript truthiness by setting the **jsTruthy** option to `true`.
+Note that LiquidJS uses Shopify's truthiness by default. It can be toggled to use standard JavaScript truthiness by setting the **jsTruthy** option to `true`.
 
 value          | truthy | falsy
 ---            | ---    | ---

docs/source/tutorials/use-in-expressjs.md

@@ -2,7 +2,7 @@
 title: Use in Express.js
 ---
 
-LiquidJS is compatible to the [express template engines](https://expressjs.com/en/resources/template-engines.html). You can set liquidjs instance to the [view engine][express-views] option:
+LiquidJS is compatible with [Express template engines](https://expressjs.com/en/resources/template-engines.html). You can set the LiquidJS instance as the [view engine][express-views] option:
 
 ```javascript
 var { Liquid } = require('liquidjs');
@@ -50,7 +50,7 @@ res.render('world')
 
 ## Caching
 
-Simply setting the [cache option][cache] to true will enable template caching, as explained in [Caching][Caching]. It's recommended to enable cache in production environment, which can be done by:
+Simply setting the [cache option][cache] to true will enable template caching, as explained in [Caching][Caching]. It's recommended to enable cache in a production environment, which can be done by:
 
 ```javascript
 var { Liquid } = require('liquidjs');

docs/source/tutorials/whitespace-control.md

@@ -13,14 +13,14 @@ By default, all tags and output markups lines will generate a NL (`\n`), and whi
 {{ author }}
 ```
 
-Outputs (note the blank link):
+Outputs (note the blank line):
 
 ```
 
 harttle
 ```
 
-We can include hyphens in your tag syntax (`{% raw %}{{-{% endraw %}`, `-}}`, `{% raw %}{%-{% endraw %}`, `-%}`) to strip whitespace from left or right. For example:
+You can include hyphens in tag syntax (`{% raw %}{{-{% endraw %}`, `-}}`, `{% raw %}{%-{% endraw %}`, `-%}`) to strip whitespace from the left or right. For example:
 
 ```liquid
 {% assign author = "harttle" -%}

docs/source/zh-cn/filters/abs.md

@@ -1,39 +0,0 @@
----
-title: abs
----
-
-{% since %}v1.9.1{% endsince %}
-
-返回数字的绝对值。
-
-输入
-```liquid
-{{ -17 | abs }}
-```
-
-输出
-```text
-17
-```
-
-输入
-```liquid
-{{ 4 | abs }}
-```
-
-输出
-```text
-4
-```
-
-对于只包含数字的字符串也好使：
-
-输入
-```liquid
-{{ "-19.86" | abs }}
-```
-
-输出
-```text
-19.86
-```

docs/source/zh-cn/filters/append.md

@@ -1,31 +0,0 @@
----
-title: append
----
-
-{% since %}v1.9.1{% endsince %}
-
-连接两个字符串并返回结果。
-
-输入
-```liquid
-{{ "/my/fancy/url" | append: ".html" }}
-```
-
-输出
-```text
-/my/fancy/url.html
-```
-
-也可以用于变量。
-
-输入
-```liquid
-{% assign filename = "/index.html" %}
-{{ "website.com" | append: filename }}
-```
-
-输出
-```text
-
-website.com/index.html
-```

docs/source/zh-cn/filters/array_to_sentence_string.md

@@ -1,27 +0,0 @@
----
-title: array_to_sentence_string
----
-
-{% since %}v10.13.0{% endsince %}
-
-把数组转化为句子，用于做标签列表。有一个可选的连接词参数。
-
-输入
-```liquid
-{{ "foo,bar,baz" | split: "," | array_to_sentence_string }}
-```
-
-输出
-```text
-foo, bar, and baz
-```
-
-输入
-```liquid
-{{ "foo,bar,baz" | split: "," | array_to_sentence_string: "or" }}
-```
-
-输出
-```text
-foo, bar, or baz
-```

docs/source/zh-cn/filters/at_least.md

@@ -1,27 +0,0 @@
----
-title: at_least
----
-
-{% since %}v8.4.0{% endsince %}
-
-限制数字到某个最小值。
-
-输入
-```liquid
-{{ 4 | at_least: 5 }}
-```
-
-输出
-```text
-5
-```
-
-输入
-```liquid
-{{ 4 | at_least: 3 }}
-```
-
-输出
-```text
-4
-```

docs/source/zh-cn/filters/at_most.md

@@ -1,27 +0,0 @@
----
-title: at_most
----
-
-{% since %}v8.4.0{% endsince %}
-
-限制数字到某个最大值。
-
-输入
-```liquid
-{{ 4 | at_most: 5 }}
-```
-
-输出
-```text
-4
-```
-
-输入
-```liquid
-{{ 4 | at_most: 3 }}
-```
-
-输出
-```text
-3
-```

docs/source/zh-cn/filters/capitalize.md

@@ -1,29 +0,0 @@
----
-title: capitalize
----
-
-{% since %}v1.9.1{% endsince %}
-
-把字符串首字母改为大写。
-
-输入
-```liquid
-{{ "title" | capitalize }}
-```
-
-输出
-```text
-Title
-```
-
-`capitalize` 只会大写首字母，因此后续单词的不会受影响：
-
- Input
-```liquid
-{{ "my great title" | capitalize }}
-```
-
-输出
-```text
-My great title
-```

docs/source/zh-cn/filters/ceil.md

@@ -1,49 +0,0 @@
----
-title: ceil
----
-
-{% since %}v1.9.1{% endsince %}
-
-向上取整，取整前 LiquidJS 会首先把输入转换为数字。
-
-输入
-```liquid
-{{ 1.2 | ceil }}
-```
-
-输出
-```text
-2
-```
-
-输入
-```liquid
-{{ 2.0 | ceil }}
-```
-
-输出
-```text
-2
-```
-
-输入
-```liquid
-{{ 183.357 | ceil }}
-```
-
-输出
-```text
-184
-```
-
-下面的例子中输入是字符串：
-
-输入
-```liquid
-{{ "3.5" | ceil }}
-```
-
-输出
-```text
-4
-```

docs/source/zh-cn/filters/cgi_escape.md

@@ -1,17 +0,0 @@
----
-title: cgi_escape
----
-
-{% since %}v10.13.0{% endsince %}
-
-把字符串 CGI 转义，用于 URL。用对应的 `%XX` 替换特殊字符，空格会被转义为 `+` 号。
-
-输入
-```liquid
-{{ "foo, bar; baz?" | cgi_escape }}
-```
-
-输出
-```text
-foo%2C+bar%3B+baz%3F
-```

docs/source/zh-cn/filters/compact.md

@@ -1,49 +0,0 @@
----
-title: compact
----
-
-{% since %}v9.22.0{% endsince %}
-
-从数组里移除任何 `null` 和 `undefined` 值。
-
-假设 `site.pages` 是网页列表，有些网页包含 `category` 属性用来标明类别。如果把它们 `map` 到数组里，那么对于没有 `category` 属性的元素就会是 `undefined`。
-
-输入
-```liquid
-{% assign site_categories = site.pages | map: "category" %}
-
-{% for category in site_categories %}
-- {{ category }}
-{% endfor %}
-```
-
-输出
-```text
-- business
-- celebrities
--
-- lifestyle
-- sports
--
-- technology
-```
-
-使用 `compact` 创建 `site_categories` 数组，可以移除所有 `null` 和 `undefined` 值。
-
-输入
-```liquid
-{% assign site_categories = site.pages | map: "category" | compact %}
-
-{% for category in site_categories %}
-- {{ category }}
-{% endfor %}
-```
-
-输出
-```text
-- business
-- celebrities
-- lifestyle
-- sports
-- technology
-```

docs/source/zh-cn/filters/concat.md

@@ -1,55 +0,0 @@
----
-title: concat
----
-
-{% since %}v2.0.0{% endsince %}
-
-连接多个数组，返回的数组包含所有传入数组的元素。
-
-输入
-```liquid
-{% assign fruits = "apples, oranges, peaches" | split: ", " %}
-{% assign vegetables = "carrots, turnips, potatoes" | split: ", " %}
-
-{% assign everything = fruits | concat: vegetables %}
-
-{% for item in everything %}
-- {{ item }}
-{% endfor %}
-```
-
-输出
-```text
-- apples
-- oranges
-- peaches
-- carrots
-- turnips
-- potatoes
-```
-
-可以链式地使用 `concat` 过滤器来连接多个数组：
-
-输入
-```liquid
-{% assign furniture = "chairs, tables, shelves" | split: ", " %}
-
-{% assign everything = fruits | concat: vegetables | concat: furniture %}
-
-{% for item in everything %}
-- {{ item }}
-{% endfor %}
-```
-
-输出
-```text
-- apples
-- oranges
-- peaches
-- carrots
-- turnips
-- potatoes
-- chairs
-- tables
-- shelves
-```

docs/source/zh-cn/filters/date.md

@@ -1,86 +0,0 @@
----
-title: date
----
-
-{% since %}v1.9.1{% endsince %}
-
-把时间戳转换为字符串。LiquidJS 尝试跟 Shopify/Liquid 保持一致，它用的是 Ruby 核心的 [Time#strftime(string)](http://www.ruby-doc.org/core/Time.html#method-i-strftime)。此外 LiquidJS 会先通过 [new Date()][newDate] 尝试把输入转换为 Date 对象。
-
-但 LiquidJS 支持的格式与 [Ruby 的 flag](https://ruby-doc.org/core/strftime_formatting_rdoc.html) 有些不同：
-  * `%Z`（自 v10.11.1 起支持）只有在传入了时区时才起作用（可以通过 `LiquidOption` 传入，也可以在创建日期时单独传入，见下文）。如果传入的时区是个数字，那么它的表现将会与 `%z` 相同。如果没有传入时区，将会返回 [运行时默认时区](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat/resolvedOptions#timezone)。
-  * LiquidJS 提供额外的 `%q` 用来处理序数：`{{ '2023/02/02' | date: '%d%q of %b'}}` => `02nd of Feb`
-* 日期字面量会通过 [new Date()][jsDate] 转化为 `Date` 对象，这意味着字面量默认使用运行时默认时区。
-* 格式字参数是可选的：
-    * 如果不传，默认为 `%A, %B %-e, %Y at %-l:%M %P %z`。
-    * 上述默认值可以通过 [`dateFormat`](/api/interfaces/LiquidOptions.html#dateFormat) 参数覆盖。
-
-输入
-```liquid
-{{ article.published_at | date: "%a, %b %d, %y" }}
-```
-
-输出
-```text
-Fri, Jul 17, 15
-```
-
-{% note info 时区 %}
-日期在输出时会转换为当地时区，设置 `timezoneOffset` LiquidJS 参数可以指定一个不同的时区。或者设置 `preserveTimezones` 为 `true` 来保持字面量时间戳的时区，数据中的日期对象不受此参数的影响。
-{% endnote %}
-
-你也可以在使用 `date` 时再设置时区：
-
-输入
-```liquid
-{{ "1990-12-31T23:00:00Z" | date: "%Y-%m-%dT%H:%M:%S", 360}} // 等价于设置 `options.timezoneOffset` to `360`.
-{{ "1990-12-31T23:00:00Z" | date: "%Y-%m-%dT%H:%M:%S", "Asia/Colombo" }}
-```
-
-输出
-```liquid
-1990-12-31T17:00:00
-1991-01-01T04:30:00
-```
-
-
-输入
-```liquid
-{{ article.published_at | date: "%Y" }}
-```
-
-输出
-```text
-2015
-```
-
-输入也可以是符合 JavaScript `Date` 格式的字符串：：
-
-输入
-```liquid
-{{ "March 14, 2016" | date: "%b %d, %y" }}
-```
-
-输出
-```text
-Mar 14, 16
-```
-
-{% note info 时间戳字符串 %}
-LiquidJS 使用 JavaScript [Date][newDate] 来解析输入字符串，意味着支持 [IETF-compliant RFC 2822 时间戳](https://datatracker.ietf.org/doc/html/rfc2822#page-14) 和 [特定版本的 ISO8601](https://www.ecma-international.org/ecma-262/11.0/#sec-date.parse)。
-{% endnote %}
-
-可以用特殊值 `"now"`（或`"today"`）来获取当前时间：
-
-输入
-```liquid
-This page was last updated at {{ "now" | date: "%Y-%m-%d %H:%M" }}.
-```
-
-输出
-```text
-This page was last updated at 2020-03-25 15:57.
-```
-
-{% note info 当前时间 %}注意得到的当前时间是模板渲染时的时间，如果你在用静态站点生成器或者模板有被缓存这一时间可能与用户看到的时间不同。{% endnote %}
-
-[newDate]: https://developer.mozilla.org/zh-CN/docs/Web/JavaScript/Reference/Global_Objects/Date

docs/source/zh-cn/filters/date_to_long_string.md

@@ -1,31 +0,0 @@
----
-title: date_to_long_string
----
-{% since %}v10.13.0{% endsince %}
-
-把日期转换为长格式（只支持 US/UK 两种），与 Jekyll 的 `date_to_long_string` 过滤器一样。
-
-输入
-```liquid
-{{ site.time | date_to_long_string }}
-```
-
-输出
-```text
-07 November 2008
-```
-
-输入
-```liquid
-{{ site.time | date_to_long_string: "ordinal" }}
-```
-
-输出
-```text
-7th November 2008
-```
-
-
-注意 JavaScript `Date` 没有时区信息，详情请参考 [date][date] 过滤器。
-
-[date]: ./date.html

docs/source/zh-cn/filters/date_to_rfc822.md

@@ -1,20 +0,0 @@
----
-title: date_to_rfc822
----
-{% since %}v10.13.0{% endsince %}
-
-把日期转换为 RFC-822 格式用于 RSS feed，与 Jekyll 的 `date_to_rfc822` 过滤器一样。
-
-输入
-```liquid
-{{ site.time | date_to_rfc822 }}
-```
-
-输入
-```text
-Mon, 07 Nov 2008 13:07:54 -0800
-```
-
-注意 JavaScript `Date` 没有时区信息，详情请参考 [date][date] 过滤器。
-
-[date]: ./date.html

docs/source/zh-cn/filters/date_to_string.md

@@ -1,30 +0,0 @@
----
-title: date_to_string
----
-{% since %}v10.13.0{% endsince %}
-
-把日期转换为短格式（只支持 US/UK 两种），与 Jekyll 的 `date_to_string` 过滤器一样。
-
-输入
-```liquid
-{{ site.time | date_to_string }}
-```
-
-输出
-```text
-07 Nov 2008
-```
-
-输入
-```liquid
-{{ site.time | date_to_string: "ordinal", "US" }}
-```
-
-输出
-```text
-Nov 7th, 2008
-```
-
-注意 JavaScript `Date` 没有时区信息，详情请参考 [date][date] 过滤器。
-
-[date]: ./date.html

docs/source/zh-cn/filters/date_to_xmlschema.md

@@ -1,20 +0,0 @@
----
-title: date_to_xmlschema
----
-{% since %}v10.13.0{% endsince %}
-
-把日期转换为 XML Schema (ISO 8601) 格式，与 Jekyll 的 `date_to_xmlschema` 过滤器一样。
-
-输入
-```liquid
-{{ site.time | date_to_xmlschema }}
-```
-
-输出
-```text
-2008-11-07T13:07:54-08:00
-```
-
-注意 JavaScript `Date` 没有时区信息，详情请参考 [date][date] 过滤器。
-
-[date]: ./date.html

docs/source/zh-cn/filters/default.md

@@ -1,64 +0,0 @@
----
-title: default
----
-
-{% since %}v1.9.1{% endsince %}
-
-在值不存在时给一个默认值，如果左侧是 [falsy][falsy] 或空（`string` 或 `Array`）就会使用这个默认值。下面的例子中 `product_price` 没有定义，因此使用了默认值。
-
-输入
-```liquid
-{{ product_price | default: 2.99 }}
-```
-
-输出
-```text
-2.99
-```
-
-下面的例子中定义了 `product_price` 所以没有使用默认值。
-
-输入
-```liquid
-{% assign product_price = 4.99 %}
-{{ product_price | default: 2.99 }}
-```
-
-输出
-```text
-4.99
-```
-
-下面例子中 `product_price` 为空，所以使用了默认值。
-
-输入
-```liquid
-{% assign product_price = "" %}
-{{ product_price | default: 2.99 }}
-```
-
-输出
-```text
-2.99
-```
-
-## 允许 `false`
-
-{% since %}v9.32.0{% endsince %}
-
-为了允许让 `false` 直接输出而不是用默认值，可以用 `allow_false` 参数。
-
-输入
-
-```liquid
-{% assign display_price = false %}
-{{ display_price | default: true, allow_false: true }}
-```
-
-输出
-
-```text
-false
-```
-
-[falsy]: ../tutorials/truthy-and-falsy.html

docs/source/zh-cn/filters/divided_by.md

@@ -1,48 +0,0 @@
----
-title: divided_by
----
-
-{% since %}v1.9.1{% endsince %}
-
-两数相除返回商，返回结果数字在 JavaScript 中 `.toString()` 得到的字符串。
-
-输入
-```liquid
-{{ 16 | divided_by: 4 }}
-```
-
-输出
-```text
-4
-```
-
-输入
-```liquid
-{{ 5 | divided_by: 3 }}
-```
-
-输出
-```text
-1.6666666666666667
-```
-
-在 JavaScript 里数字没有浮点和整数的区分，它们的类型都是 `number`：
-
-```javascript
-// always true
-5.0 === 5
-```
-
-因此如果需要做整数运算，需要传入额外的 `integerArithmetic` 参数：
-
-Input
-```liquid
-{{ 5 | divided_by: 3, true }}
-```
-
-Output
-```text
-1
-```
-
-[floor]: ./floor.html

docs/source/zh-cn/filters/downcase.md

@@ -1,27 +0,0 @@
----
-title: downcase
----
-
-{% since %}v1.9.1{% endsince %}
-
-字符串中每个字符都转为小写，对已经是小写的字符没有影响。
-
-输入
-```liquid
-{{ "Parker Moore" | downcase }}
-```
-
-输出
-```text
-parker moore
-```
-
-输入
-```liquid
-{{ "apple" | downcase }}
-```
-
-输出
-```text
-apple
-```

docs/source/zh-cn/filters/escape.md

@@ -1,27 +0,0 @@
----
-title: escape
----
-
-{% since %}v1.9.1{% endsince %}
-
-把字符串中的 HTML 特殊字符转义，对不需要转义的字符串不会产生影响。
-
-输入
-```liquid
-{{ "Have you read 'James & the Giant Peach'?" | escape }}
-```
-
-输出
-<pre class="highlight">
-{{"Have you read &#39;James &amp; the Giant Peach&#39;?" | escape}}
-</pre>
-
-输入
-```liquid
-{{ "Tetsuro Takara" | escape }}
-```
-
-输出
-```text
-Tetsuro Takara
-```

docs/source/zh-cn/filters/escape_once.md

@@ -1,27 +0,0 @@
----
-title: escape_once
----
-
-{% since %}v1.9.1{% endsince %}
-
-把字符串中的特殊字符转义得到可用在 URL 里的字符串，对已经转义过的字符串和不需要转义的字符串不会产生影响。
-
-输入
-```liquid
-{{ "1 < 2 & 3" | escape_once }}
-```
-
-输出
-<pre class="highlight">
-{{"1 &lt; 2 &amp; 3" | escape}}
-</pre>
-
-输入
-<pre class="highlight">
-&#x7B;&#x7B; "{{"1 &lt; 2 &amp; 3" | escape}}" | escape_once }}
-</pre>
-
-输出
-<pre class="highlight">
-{{"1 &lt; 2 &amp; 3" | escape}}
-</pre>

docs/source/zh-cn/filters/find.md

@@ -1,25 +0,0 @@
----
-title: find
----
-
-{% since %}v10.11.0{% endsince %}
-
-在数组中找到给定的属性为给定的值的第一个元素并返回；如果没有这样的元素则返回 `nil`。对于 `members` 数组：
-
-```javascript
-const members = [
-  { graduation_year: 2013, name: 'Jay' },
-  { graduation_year: 2014, name: 'John' },
-  { graduation_year: 2014, name: 'Jack' }
-]
-```
-
-输入
-```liquid
-{{ members | find: "graduation_year", 2014 | json }}
-```
-
-输出
-```text
-{"graduation_year":2014,"name":"John"}
-```

docs/source/zh-cn/filters/find_exp.md

@@ -1,25 +0,0 @@
----
-title: find_exp
----
-
-{% since %}v10.11.0{% endsince %}
-
-找到数组中给定的表达式值为 `true` 的第一个元素，如果没有这样的元素则返回 `nil`。对于下面的 `members` 数组：
-
-```javascript
-const members = [
-  { graduation_year: 2013, name: 'Jay' },
-  { graduation_year: 2014, name: 'John' },
-  { graduation_year: 2014, name: 'Jack' }
-]
-```
-
-输入
-```liquid
-{{ members | find_exp: "item", "item.graduation_year == 2014" | json }}
-```
-
-输出
-```text
-{"graduation_year":2014,"name":"John"}
-```

docs/source/zh-cn/filters/first.md

@@ -1,37 +0,0 @@
----
-title: first
----
-
-{% since %}v1.9.1{% endsince %}
-
-返回数组的第一个元素。
-
-输入
-```liquid
-{{ "Ground control to Major Tom." | split: " " | first }}
-```
-
-输出
-```text
-Ground
-```
-
-输入
-```liquid
-{% assign my_array = "zebra, octopus, giraffe, tiger" | split: ", " %}
-{{ my_array.first }}
-```
-
-输出
-```text
-
-zebra
-```
-
-需要在标签中使用的时候，可以用点来计算 `first`：
-
-```liquid
-{% if my_array.first == "zebra" %}
-  Here comes a zebra!
-{% endif %}
-```

docs/source/zh-cn/filters/floor.md

@@ -1,49 +0,0 @@
----
-title: floor
----
-
-{% since %}v1.9.1{% endsince %}
-
-数字下取整，LiquidJS 会尝试把输入转换为数字再做下取整操作。
-
-输入
-```liquid
-{{ 1.2 | floor }}
-```
-
-输出
-```text
-1
-```
-
-输入
-```liquid
-{{ 2.0 | floor }}
-```
-
-输出
-```text
-2
-```
-
-输入
-```liquid
-{{ 183.357 | floor }}
-```
-
-输出
-```text
-183
-```
-
-下面的例子中输入是个数字：
-
-输入
-```liquid
-{{ "3.5" | floor }}
-```
-
-输出
-```text
-3
-```

docs/source/zh-cn/filters/group_by.md

@@ -1,48 +0,0 @@
----
-title: group_by
----
-
-{% since %}v10.11.0{% endsince %}
-
-把数组元素按照给定的属性的值分组。对于 `members` 数组：
-
-```javascript
-const members = [
-  { graduation_year: 2003, name: 'Jay' },
-  { graduation_year: 2003, name: 'John' },
-  { graduation_year: 2004, name: 'Jack' }
-]
-```
-
-输入
-```liquid
-{{ members | group_by: "graduation_year" | json: 2 }}
-```
-
-输出
-```text
-[
-  {
-    "name": 2003,
-    "items": [
-      {
-        "graduation_year": 2003,
-        "name": "Jay"
-      },
-      {
-        "graduation_year": 2003,
-        "name": "John"
-      }
-    ]
-  },
-  {
-    "name": 2004,
-    "items": [
-      {
-        "graduation_year": 2004,
-        "name": "Jack"
-      }
-    ]
-  }
-]
-```

docs/source/zh-cn/filters/group_by_exp.md

@@ -1,48 +0,0 @@
----
-title: group_by_exp
----
-
-{% since %}v10.11.0{% endsince %}
-
-把数组元素按照给定的 Liquid 表达式的值分组。对于 `members` 数组：
-
-```javascript
-const members = [
-  { graduation_year: 2013, name: 'Jay' },
-  { graduation_year: 2014, name: 'John' },
-  { graduation_year: 2009, name: 'Jack' }
-]
-```
-
-输入
-```liquid
-{{ members | group_by_exp: "item", "item.graduation_year | truncate: 3, ''" | json: 2 }}
-```
-
-输出
-```text
-[
-  {
-    "name": "201",
-    "items": [
-      {
-        "graduation_year": 2013,
-        "name": "Jay"
-      },
-      {
-        "graduation_year": 2014,
-        "name": "John"
-      }
-    ]
-  },
-  {
-    "name": "200",
-    "items": [
-      {
-        "graduation_year": 2009,
-        "name": "Jack"
-      }
-    ]
-  }
-]
-```

docs/source/zh-cn/filters/inspect.md

@@ -1,42 +0,0 @@
----
-title: inspect
----
-
-{% since %}v10.13.0{% endsince %}
-
-类似于 `json`，但可以处理循环引用的情况。例如对于上下文：
-
-```
-const foo = {
-    bar: 'BAR'
-}
-foo.foo = foo
-const scope = { foo }
-```
-
-输入
-```liquid
-{% foo | inspect %}
-```
-
-输出
-```text
-{"bar":"BAR","foo":"[Circular]"}
-```
-
-## 格式化
-
-可以指定一个 `space` 参数来缩进长度。
-
-输入
-```liquid
-{{ foo | inspect: 4 }}
-```
-
-输出
-```text
-{
-    "bar": "BAR",
-    "foo": "[Circular]"
-}
-```

docs/source/zh-cn/filters/join.md

@@ -1,19 +0,0 @@
----
-title: join
----
-
-{% since %}v1.9.1{% endsince %}
-
-把数组中的元素连接成为一个字符串，以传入的参数作为分隔符。
-
-输入
-```liquid
-{% assign beatles = "John, Paul, George, Ringo" | split: ", " %}
-{{ beatles | join: " and " }}
-```
-
-输出
-```text
-
-John and Paul and George and Ringo
-```

docs/source/zh-cn/filters/json.md

@@ -1,39 +0,0 @@
----
-title: json
----
-
-{% since %}v9.10.0{% endsince %}
-
-通过 `JSON.stringify()` 把值转换为字符串，多用于调试用途。
-
-输入
-```liquid
-{% assign arr = "foo bar coo" | split: " " %}
-{{ arr | json }}
-```
-
-输出
-```text
-["foo","bar","coo"]
-```
-
-## 格式化
-
-{% since %}v10.11.0{% endsince %}
-
-可以指定一个 `space` 参数来格式化 JSON。
-
-输入
-```liquid
-{% assign arr = "foo bar coo" | split: " " %}
-{{ arr | json: 4 }}
-```
-
-输出
-```text
-[
-    "foo",
-    "bar",
-    "coo"
-]
-```

docs/source/zh-cn/filters/jsonify.md

@@ -1,9 +0,0 @@
----
-title: jsonify
----
-
-{% since %}v10.13.0{% endsince %}
-
-见 [json][json]。
-
-[json]: ./json.html

docs/source/zh-cn/filters/last.md

@@ -1,37 +0,0 @@
----
-title: last
----
-
-{% since %}v1.9.1{% endsince %}
-
-返回数组的最后一个元素。
-
-输入
-```liquid
-{{ "Ground control to Major Tom." | split: " " | last }}
-```
-
-输出
-```text
-Tom.
-```
-
-输入
-```liquid
-{% assign my_array = "zebra, octopus, giraffe, tiger" | split: ", " %}
-{{ my_array.last }}
-```
-
-输出
-```text
-
-tiger
-```
-
-需要在标签中使用的时候，可以用点来计算 `last`：
-
-```liquid
-{% if my_array.last == "tiger" %}
-  There goes a tiger!
-{% endif %}
-```

docs/source/zh-cn/filters/lstrip.md

@@ -1,17 +0,0 @@
----
-title: lstrip
----
-
-{% since %}v1.9.1{% endsince %}
-
-移除字符串左侧的空白字符（制表符、空格、换行），不影响词之间的空格。
-
-输入
-```liquid
-BEGIN{{ "          So much room for activities!          " | lstrip }}END
-```
-
-输出
-```text
-BEGINSo much room for activities!          END
-```

docs/source/zh-cn/filters/map.md

@@ -1,27 +0,0 @@
----
-title: map
----
-
-{% since %}v1.9.1{% endsince %}
-
-按照属性名提取对象的属性形成另一个数组并返回。
-
-下面的例子中假设 `site.pages` 包含了站点的所有网页元信息。使用 `assign` 加 `map` 过滤器创建了一个 `site.pages` 中所有对象的 `category` 属性的值构成的数组。
-
-输入
-```liquid
-{% assign all_categories = site.pages | map: "category" %}
-
-{% for item in all_categories %}
-- {{ item }}
-{% endfor %}
-```
-
-输出
-```text
-- business
-- celebrities
-- lifestyle
-- sports
-- technology
-```