Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removes harmful tsconfig settings #6

Merged
merged 5 commits into from
Sep 16, 2020
Merged

Removes harmful tsconfig settings #6

merged 5 commits into from
Sep 16, 2020

Conversation

fox1t
Copy link
Member

@fox1t fox1t commented Sep 15, 2020

Checklist

Fixes eslint path issues
Updates fastify-plugin in the package-lock.json to fix export default issue
Uses `import flash = require('fastify-flash') to make it work with both esModuleInterop settings
@fox1t fox1t requested review from airhorns, mcollina and Eomm September 15, 2020 15:00
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

.eslintignore Outdated Show resolved Hide resolved
@@ -6,20 +6,16 @@
"module": "commonjs",
"pretty": true,
"noEmitOnError": true,
"experimentalDecorators": true,
"sourceMap": true,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why no source maps? I think they're still relevant on the server for debugging with the devtools, or for tooling like Sentry to pull in to show you the actual source that generated an error.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do source maps even work if no src folder is shipped? Regardelss, personally, I never ship sourcemaps since there is no need for the final user to debug library code.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The source maps get written alongside the typescript compiler's output so yes they should still be included in the npm package. And I kind of feel like there isn't a downside to shipping them -- what happens if someone suspects there is a bug in this library, I feel like they would debug it wouldn't they? Especially if it's a pre-release library that has a higher likelihood of bugs, wouldn't we want to provide the best debugging experience possible?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my experience having a user that is going to debug a lib in node_modules is really rare. More often than not when something brakes they just open an issue, without even providing a repro repo.

Usually, libraries don't ship maps because they are tested and hopefully maps can't provide any useful info. Maps, of course, are mainly used for application code.

If it is important for you, we can re-add them, though.

tsconfig.json Show resolved Hide resolved
.eslintrc.js Show resolved Hide resolved
.github/workflows/ci.yml Show resolved Hide resolved
Copy link
Member

@Ethan-Arrowood Ethan-Arrowood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

all lgtm

@airhorns
Copy link
Member

LGTM!

@mcollina mcollina merged commit 50d0914 into fastify:master Sep 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Broken CI
5 participants