@fluidframework/core-interfaces
Advanced tools
Core interfaces describing the contracts the Fluid Loader supports or consumes.
See also: The Fluid Loader README.
When taking a dependency on a Fluid Framework library, we recommend using a ^ (caret) version range, such as ^1.3.4.
While Fluid Framework libraries may use different ranges with interdependencies between other Fluid Framework libraries,
library consumers should always prefer ^.
Note that when depending on a library version of the form 2.0.0-internal.x.y.z, called the Fluid internal version scheme,
you must use a >= < dependency range (such as >=2.0.0-internal.x.y.z <2.0.0-internal.w.0.0 where w is x+1).
Standard ^ and ~ ranges will not work as expected.
See the @fluid-tools/version-tools
package for more information including tools to convert between version schemes.
FAQs
Fluid object interfaces
The npm package @fluidframework/core-interfaces receives a total of 8,146 weekly downloads. As such, @fluidframework/core-interfaces popularity was classified as popular.
We found that @fluidframework/core-interfaces demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer 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
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.
