
Security News
PEP 810 Proposes Explicit Lazy Imports for Python 3.15
An opt-in lazy import keyword aims to speed up Python startups, especially CLIs, without the ecosystem-wide risks that sank PEP 690.
@fluid-experimental/devtools
Advanced tools
This library provides a developer tools suite for use alongside the Fluid Framework.
To get started, install the package by running the following command:
npm i @fluid-experimental/devtools -D
The Devtools' API surface is designed to fit nicely into most application flows.
To initialize a debugger session for your container, call initializeDevtools
.
This function accepts a DevtoolsLogger
for recording and communicating telemetry data, a list of initial Fluid Containers
to associate with the session, and (optionally) customized data visualization configurations for visualizing Container
data.
TODO: link to API docs once API shape has settled.
The Devtools object is managed as a global singleton.
That singleton is automatically cleaned up prior to the Window's "unload" event.
So typical application flows likely won't need to worry about cleanup.
That said, if you wish to have tighter control over when the Devtools are torn down, you can simply call the dispose
method on the handle returned by initialization.
This library is designed to work alongside our Chromium browser extension.
TODO: link to code on github once package names have been finalized. TODO: link to the various browsers' webstore pages for our extension once it has been publiched.
To build the package locally, first ensure you have run pnpm install
from the root of the mono-repo.
Next, to build the code, run npm run build
from the root of the mono-repo, or use fluid-build via fluid-build -s build
.
npm run build
directly within this directory for a faster build.
If you make changes to any of this package's local dependencies, you will need to run a build again from the root before building again from directly within this package.To run the tests, first ensure you have followed the build steps above.
Next, run npm run test
from a terminal within this directory.
There are many ways to contribute to Fluid.
Detailed instructions for working in the repo can be found in the Wiki.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project may contain Microsoft trademarks or logos for Microsoft projects, products, or services. Use of these trademarks or logos must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
Not finding what you're looking for in this README? Check out our GitHub Wiki or fluidframework.com.
Still not finding what you're looking for? Please file an issue.
Thank you!
This project may contain Microsoft trademarks or logos for Microsoft projects, products, or services.
Use of these trademarks or logos must follow Microsoft's Trademark & Brand Guidelines.
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
FAQs
Fluid Framework developer tools
We found that @fluid-experimental/devtools demonstrated a not healthy version release cadence and project activity because the last version was released 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
An opt-in lazy import keyword aims to speed up Python startups, especially CLIs, without the ecosystem-wide risks that sank PEP 690.
Security News
Socket CEO Feross Aboukhadijeh discusses the recent npm supply chain attacks on PodRocket, covering novel attack vectors and how developers can protect themselves.
Security News
Maintainers back GitHub’s npm security overhaul but raise concerns about CI/CD workflows, enterprise support, and token management.