new packages doesn't get indexed

[pinmosarn]

New packages doesn't get indexed, example:
I tried to use it on this package : https://www.npmjs.com/package/reponse

I used : https://api.npms.io/v2/package/reponse

but i get this error {"code":"NOT_FOUND","message":"Module not found"}

@satazor

[ruslankonev]

confirm

[antt0n]

I can confirm the problem too

[guyrotem]

+1. getting {"code":"INTERNAL","message":"Internal server error"} for any package I tried

[mt-empty]

+1, I'm getting {} for my new package even after 2 weeks.

[clearlysid]

+1 same issue 🥲

[goveo]

+1, Trying to get https://api.npms.io/v2/package/react-international-phone (since 2 months from package publish)

[Smoren]

Same issue.

Response is {"code":"NOT_FOUND","message":"Module not found"} on request to https://api.npms.io/v2/package/itertools-ts

Package is active: https://www.npmjs.com/package/itertools-ts

[AstrOOnauta]

Same issue here.

getting error: {"code":"NOT_FOUND","message":"Module not found"} on request https://api.npms.io/v2/package/react-native-international-phone-number

Package on NPM: https://www.npmjs.com/package/react-native-international-phone-number

[777arc]

Same, what's going on?

[opensrc0]

I'm having the same issue.

My Package1: https://api.npms.io/v2/package/fe-theme (Working)
My Package2: https://api.npms.io/v2/package/fe-pilot (Not working)

[fdosruiz]

Hi,

I am experiencing the same issue with my package not being found via the npms.io API. The package is published on npm and has been actively maintained with regular updates every two weeks. The package name is packetjs-di, and here is the link to it on npm:

https://www.npmjs.com/package/packetjs-di

When I query the API using https://api.npms.io/v2/package/packetjs-di, I receive the following error response:

{
  "code": "NOT_FOUND",
  "message": "Module not found"
}

I have tried:

• Republishing the package multiple times.
• Checking the package.json for any issues (it is correctly formatted).
• Testing from different networks to rule out caching issues.

It seems to be an indexing problem on npms.io's side, as the package has been live on npm for months, and everything works fine there.

I would appreciate it if this issue could be looked into. Please let me know if further information is needed to assist in resolving this.

Thank you for your help!

Best regards,