Socket
Socket
Sign inDemoInstall

@podium/utils

Package Overview
Dependencies
Maintainers
6
Versions
102
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@podium/utils - npm Package Versions

1
11

4.4.4

Diff

Changelog

Source

4.4.4 (2021-02-02)

Bug Fixes

  • deps: update dependency @podium/schemas to v4.1.1 (f2cc938)
trygve-bot
published 4.4.3 •

Changelog

Source

4.4.3 (2021-01-22)

Bug Fixes

  • deps: update dependency @podium/schemas to v4.1.0 (4ff5fe9)
trygve-bot
published 4.4.2 •

Changelog

Source

4.4.2 (2021-01-21)

Bug Fixes

  • deps: update dependency @podium/schemas to v4.0.7 (cbded99)
trygve-bot
published 4.4.1 •

Changelog

Source

4.4.1 (2020-10-28)

Bug Fixes

  • deps: update dependency camelcase to v6.2.0 (3e9dec9)
trygve-bot
published 4.4.0 •

Changelog

Source

4.4.0 (2020-10-12)

Features

BREAKING CHANGES

  • Only support node 12 and 14.

Co-authored-by: Trygve Lie trygve.lie@finn.no

  • add .buildReactLinkAttributes and .buildReactScriptAttributes methods (ffb0bff)
  • add .toReactAttrs() method to AssetJs and AssetCss classes and integration tests (7ab097f)
trygve-bot
published 4.3.3 •

Changelog

Source

4.3.3 (2020-10-10)

Bug Fixes

  • deps: update dependency @podium/schemas to v4.0.5 (9bf1a14)
trygve-bot
published 4.3.2 •

Changelog

Source

4.3.2 (2020-10-10)

Bug Fixes

  • deps: update dependency camelcase to v6.1.0 (ef22149)
trygve-bot
published 4.3.1 •

Changelog

Source

4.3.1 (2020-09-13)

Bug Fixes

  • deps: update dependency @podium/schemas to v4.0.4 (5ff49c0)
trygve-bot
published 5.0.0-next.3 •

Changelog

Source

5.0.0-next.3 (2020-07-27)

Features

  • Use ES private properties instead of Symbols for privacy (#72) (4083fa1)

BREAKING CHANGES

  • Due to dropping node 10.x support we use ES private properties instead of Symbols.

We've been using Symbols to define private properties in classes up until now. This has the downside that they are not true private and in later versions of node.js one would see these Symbols when inspecting an object. What we want is proper private properties.

This PR does also add a pretty printer which outputs an object literal or the object so when debugging one can see the getters and setters of the object.

Example: printing a object with console.log() would previously print the following:

PodiumHttpIncoming {
  [Symbol(podium:httpincoming:development)]: false,
  [Symbol(podium:httpincoming:response)]: {},
  [Symbol(podium:httpincoming:request)]: {},
  [Symbol(podium:httpincoming:context)]: {},
  [Symbol(podium:httpincoming:params)]: {},
  [Symbol(podium:httpincoming:proxy)]: false,
  [Symbol(podium:httpincoming:name)]: '',
  [Symbol(podium:httpincoming:view)]: {},
  [Symbol(podium:httpincoming:url)]: {},
  [Symbol(podium:httpincoming:css)]: [],
  [Symbol(podium:httpincoming:js)]: []
}

Now the following will be printed:

{
  development: false,
  response: {},
  request: {},
  context: {},
  params: {},
  proxy: false,
  name: '',
  view: {},
  url: {},
  css: [],
  js: []
}

Co-authored-by: Trygve Lie trygve.lie@finn.no

trygve-bot
published 5.0.0-next.2 •

Changelog

Source

5.0.0-next.2 (2020-07-15)

Bug Fixes

  • Simplify js and css value validation (#70) (05a1ffc)
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc