Stuck on an issue?
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.
Change configuration file name from `llama-pack-config.json` to `bubblewrap-config.json`
See original GitHub issueAs the project name and its CLI command has been changed from llama-pack to bubblewrap , we should those name calls everywhere to avoid any confusions
Possible places to change - llama-pack.config.json which contains the dependency directory.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Provide paths to JDK and Android tools and environment ...
bubblewrap will read the JDK and Android SDK path from ~/llama-pack/llama-pack-config.json if it is available. Example file:.
Read more >@bubblewrap/cli - npm
Regenerates the Android project files from a twa-manifest.json file. Usage: bubblewrap update [--appVersionName="<version-string>"] [-- ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It sounds to me we should:
Closed via #198