fix npm publish nil pointer dereference

[reshmifrog]

• All tests passed. If this feature is not already covered by the tests, I added new tests.
• All static analysis checks passed.
• Appropriate label is added to auto generate release notes.
• I used gofmt for formatting the code before submitting the pull request.
• PR description is clear and concise, and it includes the proposed solution/fix.

---

Problem: Invalid memory address or nil pointer dereference during jf npm publish
Solution: we were iterating over a list of readers and calling methods on them without checking if any reader was nil, causing a crash. Added a check to skip nil readers instead of crashing.