Publish generated source maps to NPM

[mdwheele]

Hello!

💁‍♀️ This PR removes the *.map rule from .npmignore with the intent that source maps are published in future NPM releases.

I somewhat-often find myself setting breakpoints in dependencies during development to either be able to trace what seems like a bug or simply to figure out how a dependency is working in order to be able to contribute. Today, when I launch my debugger, I get a slew of "errors" complaining about not being able to find source maps for this package:

Could not read source map for file:///<snip>/node_modules/express-openapi-validator/dist/index.js: 
ENOENT: no such file or directory, open '<snip>/node_modules/express-openapi-validator/dist/index.js.map'

This repeats for basically every file in dist.

There may be more to this PR than simply removing the *.map rule, but I would propose that source maps should be distributed as part of the NPM release process and this seemed like the first step. As far as I can tell, the tsconfig is already configured to generate source maps.

Please let me know if there's further work to be done here and I'll be happy to help!

[mdwheele]

Hey @cdimascio! Just checking in to see if there's anything I can do to help out here. Hope all is well!

[cdimascio]

hey @mdwheele, i'll publish an alpha version with your change. perhaps you can verify whether the maps work

[cdimascio]

@mdwheele, please try npm install express-openapi-validator@4.12.7-alpha.1. let me know your results.

[mdwheele]

This works great!

[cdimascio]

thanks @mdwheele
will get this merged

[mdwheele]

🎉 Thanks so much!