Can't resolve module after npm install

[FloweryScythe13]

Module not found: Can't resolve 'react-typescript-pdf-reader' in 'C:\Users\brichem\.....\src\components'

I notice that there appears to be no valid entry point specified in package.json for the npm module. My install comes only with the /assests and /demo folders, not any others containing the distribution code. Perhaps this is the reason that Node cannot find the module for me?

[sumn2u]

@FloweryScythe13 are you sure react-typescript-pdf-reader is installed correctly? you can look into the node_modules folder, if it is installed correctly then it should show you other files too.

[FloweryScythe13]

@sumn2u That's part of what I'm wondering. I have installed and uninstalled react-typescript-pdf-reader several times, and I can see it in the node_modules folder, but like I said, the installed package contains code only under the /assests and /demo folders. main in package.json points to a build/index.js file, but no path exists in the module. The whole installed module in node_modules looks like this:

• react-typescript-pdf-reader
  • assests
  • react-pdf.png
  • demo
  • css
  • fonts
  • 0.index.js
  • 0.index.js.map
  • .... (other files)
  • CHANGELOG.md
  • LICENSE
  • package.json
  • README.md
  • yarn.lock

This is happening on the NPM runkit too: https://npm.runkit.com/react-typescript-pdf-reader So maybe some of the needed files are missing in the NPM registry for react-typescript-pdf-reader?

[tynarbekov]

@FloweryScythe13 I have same problem now, could solve this problem ?

[FloweryScythe13]

@tynarbekov From what I recall finding at the time, this repo's published npm package really is incomplete and broken. Only someone with the access necessary to update the package in the global npm registry can fix this. I'm guessing the only person who can do that is @sumn2u .

[sumn2u]

let me have a look into this @FloweryScythe13 @tynarbekov