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.
javascript: required-only not working
See original GitHub issueStarting with 4.0.37 cdxgen --required-only does not “find” any dependencies for javascript projects.
Instead it errors with the message:
Unable to produce BOM for .
Try running the command with -t <type> or -r argument
Providing type or recursion option does not remediate this problem.
I think it may have something to do with the implementation of #164.
With best regards…
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
required not working when if is used in javascript
I am making a simple registration form, when I remove the if statements from "from here" comment to "to here" comment, the required...
Read more >required-only doesn't include transitive dependencies · Issue ...
The problem is that it doesn't include the dependencies of the dependencies it finds... and it needs to do so as those transitive...
Read more >Bootstrap 3.3.4 accordion with arrow glyphs - Only CSS
Bootstrap 3.3.4 accordion with arrow glyphs - No JS required - Only CSS...
Read more >Show/hide field javascript not working for required field
another question: on the list form, i want to make the hidden fields required only when they show on the form. Thanks in...
Read more >Why Gatsby is better with JavaScript
Gatsby sites can work without JavaScript, however they will often be ... JavaScript is required only for additional interactive elements of ...
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
Thank you @prabhu for your kind support. I can confirm that the bug was still present in 4.0.43 and is now resolved in 4.0.44.
@stexandev This was indeed a bug. I’ve released 4.0.44, including the fix and GitHub actions support. Could you kindly retest and confirm?