Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump the npm_and_yarn group across 1 directory with 2 updates #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Bump the npm_and_yarn group across 1 directory with 2 updates #2

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Sep 23, 2024

Bumps the npm_and_yarn group with 2 updates in the / directory: dustjs-linkedin and lodash.

Updates dustjs-linkedin from 2.5.1 to 3.0.1

Release notes

Sourced from dustjs-linkedin's releases.

v3.0.1

What's Changed

Full Changelog: linkedin/dustjs@v3.0.0...v3.0.1

v3.0.0

What's Changed

New Contributors

Full Changelog: linkedin/dustjs@v2.7.2...v3.0.0

v2.7.2

Notable Changes

Filters

Dust filter functions previously took one argument, the string to filter. They now accept a second argument, which is the current context.

Helpers

Dust helpers can now return primitives.

Helpers act like references or sections depending on if they have a body. When they have no body, they act like a reference and look in params.filters for filters to use. When they have a body, they act like a section. You can return thenables and streams normally.

{@return value="" filters="|s" /} 
{@return value=""}{.} World{/return}

v2.7.1

Notable Changes

dust.config.cache

In previous versions, setting dust.config.cache to false would blow away the entire cache on every render. Now, setting it to false just prevents new templates from being added and cached templates from being used. Setting it back to true means that previously-cached templates will be ready to use.

... (truncated)

Changelog

Sourced from dustjs-linkedin's changelog.

v3.0.1 (2021/12/29 18:20 +00:00)

v3.0.0 (2021/10/20 22:56 +00:00)

list (2016/12/08 20:15 +00:00)

v2.7.4 (2016/09/13 02:52 +00:00)

  • #744 Don't use instanceof to determine if a Context is a Context. Instead use a flag on the instance itself so it can survive object merges. (@​sethkinast)

v2.6.3 (2016/07/26 18:03 +00:00)

v2.7.2 (2015/06/08 20:41 +00:00)

  • #673 Pass the current context to filters (@​sethkinast)
  • #676 If a Promise is resolved with an array, iterate over it instead of rendering the whole array at once.

Closes #674 (@​sethkinast)

  • #647 Allow helpers to return primitives

Previously returning a primitive would crash rendering with no way to recover. You can still return a Chunk and do more complex work if you need to.

Helpers act like references or sections depending on if they have a body. When they have no body, they act like a reference and look in params.filters for filters to use. When they have a body, they act like a section. You can return thenables and streams normally.

{@​return value="" filters="|s" /} {@​return value=""}{.} World{/return}

Closes #645 (@​sethkinast)

  • #664 Be slightly pickier about what Dust thinks a Stream is.

Closes #663 (@​sethkinast)

Closes #649 Closes #602 Closes #642 (@​sethkinast)

  • #660 Grammar: s/char/character/ to avoid using a reserved name

Closes #659 (@​sethkinast)

v2.7.1 (2015/04/30 20:32 +00:00)

  • #655 Update CommonJS example to make use of new onLoad behavior (@​sethkinast)
  • #653 Fix array iteration when context is undefined (@​sethkinast)
  • #641 Add a cb(null, compiledTemplate) signature to dust.onLoad

Calling the onLoad callback with a compiled template function will use this template to satisfy the load request. The template is not automatically registered under any name when passed to the callback, so the onLoad function should handle registration as it needs.

dust.cache behavior has been changed slightly. Before, setting it to false would blow away the entire cache on every render. Now, setting it to false just prevents new templates from being added and cached templates from being used, but if it's set to true again previously-cached templates will be ready to use. (@​sethkinast)

v2.7.0 (2015/04/17 23:23 +00:00)

  • dust.render and dust.stream now accept a compiled template function in addition to a template name.
  • dust.compile no longer requires a template name, and will compile an anonymous template without one (so --name is no longer required for dustc either)
  • dust.load is removed from the public API
  • dust.renderSource is moved to the compiler, so it's only included in dust-full now (Fixes #412)
  • dust.compileFn is moved to the compiler, so it's only included in dust-full now
  • add dust.isTemplateFn
  • add dust.config.cache = true, set to false to disable caching and load templates again every time (Fixes #451)
  • add dust.config.cjs = false, set to true to compile templates as CommonJS modules
  • add --cjs flag to dustc
  • Move a bunch of exposed compiler stuff under dust.compiler (but leave it exposed until 2.8) (@​sethkinast)

... (truncated)

Commits
  • 5cd5529 Release v3.0.1
  • 0d72e0b Merge pull request #808 from sumeetkakkar/topic/update-deps
  • b2aaa47 Merge branch 'master' into topic/update-deps
  • bd397ea Update tests.yaml: add --legacy-peer-deps to support npm 8 restrictions
  • 115f78c dependency update: chokidar
  • d951a90 Update tests.yml
  • ea9ae70 Create tests.yml
  • 2e8795c Release v3.0.0
  • 6f98371 merge from 2.7
  • db6d8b9 Merge pull request #805 from sumeetkakkar/fix/proto-pollution
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by krakenjs-user, a new releaser for dustjs-linkedin since your current version.


Updates lodash from 2.4.2 to 4.17.21

Release notes

Sourced from lodash's releases.

4.0.0

lodash v4.0.0

2015 was big year! Lodash became the most depended on npm package, passed 1 billion downloads, & its v3 release saw massive adoption!

The year was also one of collaboration, as discussions began on merging Lodash & Underscore. Much of Lodash v4 is proofing out the ideas from those discussions. Lodash v4 would not be possible without the collaboration & contributions of the Underscore core team. In the spirit of merging our teams have blended with several members contributing to both libraries.

For 2016 & lodash v4.0.0 we wanted to cut loose, push forward, & take things up a notch!

Modern only

With v4 we’re breaking free from old projects, old environments, & dropping old IE < 9 support!

4 kB Core

Lodash’s kitchen-sink size will continue to grow as new methods & functionality are added. However, we now offer a 4 kB (gzipped) core build that’s compatible with Backbone v1.2.4 for folks who want Lodash without lugging around the kitchen sink.

More ES6

We’ve continued to embrace ES6 with methods like _.isSymbol, added support for cloning & comparing array buffers, maps, sets, & symbols, converting iterators to arrays, & iterable _(…).

In addition, we’ve published an es-build & pulled babel-plugin-lodash into core to make tree-shaking a breeze.

More Modular

Pop quiz! 📣

What category path does the bindAll method belong to? Is it

A) require('lodash/function/bindAll') B) require('lodash/utility/bindAll') C) require('lodash/util/bindAll')

Don’t know? Well, with v4 it doesn’t matter because now module paths are as simple as

var bindAll = require('lodash/bindAll');

We’ve also reduced module complexity making it easier to create smaller bundles. This has helped Lodash adoption with libraries like Async & Redux!

1st Class FP

With v3 we introduced lodash-fp. We learned a lot & with v4 we decided to pull it into core.

Now you can get immutable, auto-curried, iteratee-first, data-last methods as simply as

var _ = require('lodash/fp');
var object = { 'a': 1 };
</tr></table>

... (truncated)

Commits
  • f299b52 Bump to v4.17.21
  • c4847eb Improve performance of toNumber, trim and trimEnd on large input strings
  • 3469357 Prevent command injection through _.template's variable option
  • ded9bc6 Bump to v4.17.20.
  • 63150ef Documentation fixes.
  • 00f0f62 test.js: Remove trailing comma.
  • 846e434 Temporarily use a custom fork of lodash-cli.
  • 5d046f3 Re-enable Travis tests on 4.17 branch.
  • aa816b3 Remove /npm-package.
  • d7fbc52 Bump to v4.17.19
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by bnjmnt4n, a new releaser for lodash since your current version.


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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
Bump the npm_and_yarn group across 1 directory with 2 updates
e5552fe 
Bumps the npm_and_yarn group with 2 updates in the / directory: [dustjs-linkedin](https://github.com/linkedin/dustjs) and [lodash](https://github.com/lodash/lodash).


Updates `dustjs-linkedin` from 2.5.1 to 3.0.1
- [Release notes](https://github.com/linkedin/dustjs/releases)
- [Changelog](https://github.com/linkedin/dustjs/blob/master/CHANGELOG.md)
- [Commits](linkedin/dustjs@v2.5.1...v3.0.1)

Updates `lodash` from 2.4.2 to 4.17.21
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@2.4.2...4.17.21)

---
updated-dependencies:
- dependency-name: dustjs-linkedin
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: lodash
  dependency-type: direct:production
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 23, 2024
@dependabot dependabot bot mentioned this pull request Sep 23, 2024
Closed
@socket-security Socket Security
Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/dustjs-linkedin@3.0.1 unsafe Transitive: environment, filesystem +28 1.34 MB krakenjs-user
npm/lodash@4.17.21 None 0 1.41 MB bnjmnt4n

🚮 Removed packages: npm/dustjs-linkedin@2.5.1, npm/lodash@2.4.2

View full report↗︎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants