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.
Readme doesn't include "es" format
See original GitHub issueThe description of the format option, in the readme file is:
--format— format of the generated parser:amd,commonjs,globals,umd(default:commonjs)
But Peggy includes an es option as well.
It’s worth noting that the CLI documentation does have the es type listed:
Format of the generated parser:
amd,commonjs,globals,umd,es(default:commonjs).
But, the dependencies section for the JS API says:
valid only when format is set to “amd”, “commonjs”, or “umd”
Where it should include es" in the list.
I could try and get a PR in to fix these things, but I’m not sure when I’ll get the time to do so.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
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
How about we just accept our status quo for now, document it, and clean it up later if it becomes a problem. We can always add an alias later.
seems fine. i was just appealing for community norms, and it seems there isn’t one