You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It would be useful for robot-framework-browser-extensions if rfbrowser init would allow for an additional path to a package.json used by the browser extensions. That would make that the node packages will all live in the same location, which I think is preferable. It would also ease the use of extensions
Describe the solution you'd like
I'd like something like
Describe alternatives you've considered
Alternatives are folks having to manually install and debug the package installation themselves and you're likely to end up with multiple node-modules folders in your project, which I consider undesirable.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It would be useful for robot-framework-browser-extensions if
rfbrowser init
would allow for an additional path to a package.json used by the browser extensions. That would make that the node packages will all live in the same location, which I think is preferable. It would also ease the use of extensionsDescribe the solution you'd like
I'd like something like
usage:
rfbrowser init skip_browser_install file="path/to/extensions/package.json"
Describe alternatives you've considered
Alternatives are folks having to manually install and debug the package installation themselves and you're likely to end up with multiple
node-modules
folders in your project, which I consider undesirable.The text was updated successfully, but these errors were encountered: