Bump liquidjs from 9.22.1 to 10.0.0

[dependabot]

Bumps liquidjs from 9.22.1 to 10.0.0.

Release notes

Sourced from liquidjs's releases.

v10.0.0

10.0.0 (2022-11-27)

chore

• rename filters to snake style, #487 (ff112a4)

Code Refactoring

• _evalToken renamed to evalToken (4e1a30a)
• change ownPropertyOnly default value to true (7eb6216)
• delay creation of operatorsTrie and hide this implementation (bb58d3e)
• remove toThenable export (ffefd91)
• remove use of internal Context class in evalValue argument (b115077)

Performance Improvements

• target Node.js 14 for cjs bundle (main entry) (1f6ce7c)

BREAKING CHANGES

• evalToken now returns a generator (LiquidJS async), which is different from evalToken in previous LiquidJS versions.
• main entry need Node.js>=14 to run, you can build LiquidJS by your own by using ESM entry.
• ownPropertyOnly default value changed to true
• <liquidjs>.toThenable is removed, use <liquidjs>.toPromise instead
• evalValue won't support Context as second argument anymore.
• use operators instead of operatorsTrie as Tokenizer constructor argument, #500
• keys in <liquidjs>.filters are now in snake case (instead of camel case), identical to that in Liquid template.

v9.43.0

9.43.0 (2022-11-27)

Features

• support timezone offset argument for date filter, #553 (7a71485)

v9.42.1

9.42.1 (2022-10-21)

Bug Fixes

• truncatewords should use at least one word, #537 (32f613f)

v9.42.0

... (truncated)

Changelog

Sourced from liquidjs's changelog.

10.0.0 (2022-11-27)

Code Refactoring

• rename filters to snake style, #487 (ff112a4)
• _evalToken renamed to evalToken (4e1a30a)
• change ownPropertyOnly default value to true (7eb6216)
• delay creation of operatorsTrie and hide this implementation (bb58d3e)
• remove toThenable export (ffefd91)
• remove use of internal Context class in evalValue argument (b115077)

Performance Improvements

• target Node.js 14 for cjs bundle (main entry) (1f6ce7c)

BREAKING CHANGES

• evalToken now returns a generator (LiquidJS async), which is different from evalToken in previous LiquidJS versions.
• main entry need Node.js>=14 to run, you can build LiquidJS by your own by using ESM entry.
• ownPropertyOnly default value changed to true
• <liquidjs>.toThenable is removed, use <liquidjs>.toPromise instead
• evalValue won't support Context as second argument anymore.
• use operators instead of operatorsTrie as Tokenizer constructor argument, #500
• keys in <liquidjs>.filters are now in snake case (instead of camel case), identical to that in Liquid template.

9.43.0 (2022-11-27)

Features

• support timezone offset argument for date filter, #553 (7a71485)

9.42.1 (2022-10-21)

Bug Fixes

• truncatewords should use at least one word, #537 (32f613f)

9.42.0 (2022-08-27)

Features

• promise in expression & nested property, #533 #276 (bbf00f3)

9.41.0 (2022-08-24)

... (truncated)

Commits

• 9b9ef37 chore(release): 10.0.0 [skip ci]
• 5bbdc08 chore(deps): bump minimatch from 3.0.4 to 3.1.2
• 1380ac9 refactor: more consistent tags to make it easier to iterate over, #524
• 4e1a30a refactor: _evalToken renamed to evalToken
• 9299268 refactor: Tag class support in registerTag()
• 1f6ce7c perf: target Node.js 14 for cjs bundle (main entry)
• 7eb6216 refactor: change ownPropertyOnly default value to true
• ffefd91 refactor: remove toThenable export
• b115077 refactor: remove use of internal Context class in evalValue argument
• bb58d3e refactor: delay creation of operatorsTrie and hide this implementation
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

[changelogg]

Hey! Changelogs info seems to be missing or might be in incorrect format.
Please use the below template in PR description to ensure Changelogg can detect your changes:
- (tag) changelog_text
or
- tag: changelog_text
OR
You can add tag in PR header or while doing a commit too
(tag) PR header
or
tag: PR header
Valid tags: added / feat, changed, deprecated, fixed / fix, removed, security, build, ci, chore, docs, perf, refactor, revert, style, test
Thanks!
For more info, check out changelogg docs

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[performance-testing-bot]

Unable to locate .performanceTestingBot config file

[vizipi]

Pull request analysis by VIZIPI

Below you will find who is the most qualified team member to review your code.
This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below )   Feedback always welcome

Reviewers with knowledge related to these changes

Match %	Person	Commit Count	Common Files
100.00 %	Jason Etcovitch	17	2
100.00 %	Sarah Schneider	14	2
100.00 %	Kevin Heis	12	2
100.00 %	James M. Greene	8	2
100.00 %	Rachael Sewell	7	2
100.00 %	Lucas Costi	6	2

---

Potential missing files from this Pull request

No commonly committed files found with a 40% threashold

---

Committed file ranks

(click to expand)

100.00%[package.json]

99.99%[package-lock.json]