weave 0.0.0-d10e24e0799cbeaccb82adf274ff03a8533e9f7f
Install from the command line:
Learn more about npm packages
$ npm install @wandb/weave@0.0.0-d10e24e0799cbeaccb82adf274ff03a8533e9f7f
Install via package.json:
"@wandb/weave": "0.0.0-d10e24e0799cbeaccb82adf274ff03a8533e9f7f"
About this version
This module contains the public-facing @wandb/weave library. This code used to live in app, but was moved here so it could be bundled with the weave python package.
See PR https://github.com/wandb/core/pull/8926 for details.
I am a frontend developer. How will the migration from app -> @wandb/weave affect my development workflow?
The only effect this refactor should have on your development is that it changes where you import certain objects from. Instead of doing
import makeComp from '../util/profiler';you would now do
import makeComp from '@wandb/weave/common/util/profiler';This change does not:
- Change any of the commands you use to build, lint, test, install, or deploy the application
- Add any additional devops steps to the local development workflow
- Add additional dependencies for you to manage
- Require you to perform any migrations
- Alter the functionality of the application
It only changes where certain code lives.
Only put things into common/ if they are also needed by @wandb/weave. If something you have written is not needed by @wandb/weave, just put it in app/.
Assets
- weave-0.0.0-d10e24e0799cbeaccb82adf274ff03a8533e9f7f.tgz
Download activity
- Total downloads 0
- Last 30 days 0
- Last week 0
- Today 0