Insert a proper flipper-plugin version
Summary: `flipper-pkg init` would always introduce `flipper-plugin` peer with version `latest`. Since that can never be checked against the current flipper version, it always generated a warning. Updated the init process to take the version the plugin was generated with as base version instead. Note that in the test the version will always display as 0.0.0, will double check after release that the proper version will show up when running from npx, but don't see a reason why not (famous last words) Reviewed By: nikoant, priteshrnandgaonkar Differential Revision: D28992531 fbshipit-source-id: c32aad1650f575f790c2e04d089104b7a616d26f
This commit is contained in:
committed by
Facebook GitHub Bot
parent
02d80526e3
commit
f7732ed4fd
@@ -18,7 +18,10 @@ on the desktop side.
|
||||
|
||||
## Scaffolding a new Desktop plugin
|
||||
|
||||
A new Flipper Desktop plugin can be scaffolded by running `npx flipper-pkg init` in the directory where you want to store the plugin sources (Don't run this command inside the Flipper repository itself!). For example:
|
||||
A new Flipper Desktop plugin can be scaffolded by running `npx flipper-pkg init` in the directory where you want to store the plugin sources (Don't run this command inside the Flipper repository itself!).
|
||||
Before running this command, make sure Flipper is closed.
|
||||
|
||||
For example:
|
||||
|
||||
```bash
|
||||
mkdir ~/FlipperPlugins
|
||||
|
||||
Reference in New Issue
Block a user