Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@bedrock/core

Package Overview
Dependencies
Maintainers
5
Versions
19
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@bedrock/core - npm Package Versions

2

6.3.0

Diff

Changelog

Source

6.3.0 - 2024-11-19

Added

  • Add bedrock.shutdown() call that performs an orderly shutdown and emits various events. This differs from exit() and process.exit() which are more immediate.
  • Add bedrock.stopped event, emitted before bedrock.exit.
  • Add documentation for bedrock.stop, bedrock.stopped, and bedrock.exit events.

Changed

  • Deprecate undocumented bedrock-cli.exit event. Use bedrock.exit instead. If there is use case for this specific event, please file an issue.
dlongley
published 6.2.0 •

Changelog

Source

6.2.0 - 2024-10-15

Changed

  • Use serialize-error@11. No significant changes are expected.

Fixed

  • Replace unmaintained uid-number package with passwd-user.
dlongley
published 6.1.3 •

Changelog

Source

6.1.3 - 2024-03-06

Fixed

  • Move eslint plugin to devDependencies.
dlongley
published 6.1.2 •

Changelog

Source

6.1.2 - 2024-02-28

Fixed

  • Publish proper LICENSE file.
dlongley
published 6.1.1 •

Changelog

Source

6.1.1 - 2024-02-27

Fixed

  • Relicense under the Apache-2.0 license.
dlongley
published 6.1.0 •

Changelog

Source

6.1.0 - 2024-02-12

Changed

  • Open Source under BSD-3-Clause license.
  • Bump package.json Node.js version to 18.x (LTS).
dlongley
published 6.0.1 •

Changelog

Source

6.0.1 - 2022-04-29

Fixed

  • Fix default CLI command.
dlongley
published 6.0.0 •

Changelog

Source

6.0.0 - 2022-04-28

Changed

  • BREAKING: A number of changes have been made to BedrockError to bring it more inline with modern JavaScript errors and common practice and conventions within bedrock applications. Many of these changes are unlikely to break existing applications, but they could, so they are listed here.
    • toObject conversion now uses serialize-error internally for representing error stack traces.
    • A private or unspecified BedrockError, when converted to an object, now has a type of OperationError (instead of bedrock.InternalServerError. Most bedrock applications do not read or switch off of this value.
    • Using an array for the name of a BedrockError is disallowed, it must be a string. This usage is uncommon and unlikely to impact most applications.
    • When BedrockError is converted to an object, it includes both name and type (as the same value). The use of name is preferred, but type is preserved for backwards compatibility. Applications that strictly disallowed additional properties on errors will need to allow the name property to be present, but the name property is built into JavaScript errors and allowing for additional properties in errors is common practice such that this change is unlikely to affect many applications. The type property may be removed in the future, so applications should normalize to using name.
    • isType, hasType, hasCauseOfType have been removed. Use the nullish coalescing operator and compare against name instead. Subtle mistakes can also be made by writing code that is not specific to the location that particular errors occur in a causal chain, so these functions have been removed to avoid those problems. These functions are already rarely used in modern bedrock modules and applications.
  • BREAKING: Top-level variables used in computed config templates must use valid JavaScript variable names, e.g., they cannot include hyphens (-) or periods (.). A future version may remove compute config templates entirely; functions should be used instead for computed configs.
  • BREAKING: config.paths.cache and config.paths.log are now listed as requiring overriding in deployments. This replaces the custom code that would log a warning if they were not set.
  • BREAKING: Use commander@9. An important change is that bedrock.program no longer has properties for command line options, those are accessed via bedrock.program.opts() instead. See: https://github.com/tj/commander.js/blob/master/CHANGELOG.md
  • Calling bedrock.start more than once will cause an error to be thrown. This was already not supported and caused non-deterministic broken behavior, this change just makes it explicit and deterministic (the same clear error is always thrown).
  • Replace error serializer/deserializer errio with serialize-error. Should not be a breaking change.

Removed

  • BREAKING: Remove winston mail transport. The winston mail transport which is disabled by default and not expected to be used in any applications using 5.x has been removed.
  • BREAKING: Remove bedrock.util.callbackify. Import from node.js util if needed.
  • BREAKING: Remove bedrock.util.hasValue.
  • BREAKING: Remove bedrock.util.delay. Import from npm delay package if needed.
  • BREAKING: Remove bedrock.util.uuid. Import from npm uuid package if needed.
  • BREAKING: Remove bedrock.util.w3cDate.
  • BREAKING: Remove bedrock.util.isObject.
  • BREAKING: Remove bedrock.util.clone. Import from npm klona package if needed.
  • BREAKING: Remove bedrock.util.boolify.
  • BREAKING: Remove runOnceAsync. Use runOnce instead.
  • BREAKING: Remove support for callback-based async event listeners. These are not supported and use of them may cause breakage.
dlongley
published 5.1.1 •

Changelog

Source

5.1.1 - 2022-04-13

Fixed

  • Fix imports.
dlongley
published 5.1.0 •

Changelog

Source

5.1.0 - 2022-04-13

Changed

  • Update dependencies:
    • @digitalbazaar/async-node-events.
    • commander@2.
2
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