Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Get rid of rfbrowser init
See original GitHub issueI am currently making a conda package for robotframework-browser: https://github.com/conda-forge/staged-recipes/pull/13300
It should soon be possible for users to run the following in order to get it to work:
conda install -c conda-forge robotframework-browser
Note that this does not require nodejs to be installed on the user machine, which is convenient, because it’s not required to run rfbrowser init.
In this issue, I would like to suggest getting rid of rfbrowser init. My idea is that we could run npm install --production in the setup.py directly, this would mean that:
pip install robotframework-browserwill be enough to get it to work- it’s not required any more that the user machine has
nodejsinstalled, only the dev machine (when making the release or when making a dev install)
Please tell me what you think.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@martinRenou Yeah pkg achieves shipping of a single binary containing all JS code and a bundled node runtime.
Sorry, I see this issue is actually a duplicate of #465