Security News
GitHub Removes Malicious Pull Requests Targeting Open Source Repositories
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
@smithy/core
Advanced tools
[![NPM version](https://img.shields.io/npm/v/@smithy/core/latest.svg)](https://www.npmjs.com/package/@smithy/core) [![NPM downloads](https://img.shields.io/npm/dm/@smithy/core.svg)](https://www.npmjs.com/package/@smithy/core)
An internal package. You probably shouldn't use this package, at least directly.
This package provides common or core functionality for generic Smithy clients.
You do not need to explicitly install this package, since it will be installed during code generation if used.
@smithy/core
submodulesCore submodules are organized for distribution via the package.json
exports
field.
exports
is supported by default by the latest Node.js, webpack, and esbuild. For react-native, it can be
enabled via instructions found at reactnative.dev/blog, but we also provide a compatibility redirect.
Think of @smithy/core
as a mono-package within the monorepo.
It preserves the benefits of modularization, for example to optimize Node.js initialization speed,
while making it easier to have a consistent version of core dependencies, reducing package sprawl when
installing a Smithy runtime client.
index.ts
file corresponding to the pattern ./src/submodules/<MODULE_NAME>/index.ts
will be
published as a separate dist-cjs
bundled submodule index using the Inliner.js
build script../src/submodules/<SUBMODULE>
including an index.ts
file and a README.md
file.
package.json
and the various tsconfig.json
files, but it will automatically fix them if possible.@smithy/<pkg>
package in that importing it in Node.js will resolve a separate bundle.@scope/pkg/submodule
name as the import.
@smithy/core
.
The linter runs during yarn build
and also as yarn lint
.@smithy/core/submodule
vs. @smithy/new-package
?Keep in mind that the core package is installed by all downstream clients.
If the component functionality is upstream of multiple clients, it is
a good candidate for a core submodule. For example, if middleware-retry
had been written
after the support for submodules was added, it would have been a submodule.
If the component's functionality is downstream of a client (rare), or only expected to be used by a very small subset of clients, it could be written as a standalone package.
FAQs
[![NPM version](https://img.shields.io/npm/v/@smithy/core/latest.svg)](https://www.npmjs.com/package/@smithy/core) [![NPM downloads](https://img.shields.io/npm/dm/@smithy/core.svg)](https://www.npmjs.com/package/@smithy/core)
The npm package @smithy/core receives a total of 8,470,908 weekly downloads. As such, @smithy/core popularity was classified as popular.
We found that @smithy/core demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.