-
-
Notifications
You must be signed in to change notification settings - Fork 594
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
Export defaults
from node-resolve
plugin
#299
Comments
Thanks for the issue. Please expand on your use case further, I don't quite understand what you're trying to do. More code would definitely help. |
Sorry if I wasn't clear enough. For I could copy and paste defaults and add my custom extensions but I feel like this could be improved if those defaults were exported for me to reuse them. You can see the example here: https://github.com/kentcdodds/kcd-scripts/pull/131/files#diff-a1cfe028f2f056e2d30db017481d4ad0R146-R150 |
Thanks for explaining the use case further. Would it be more useful to expose defaults, or do a deep merge on the defaults and options? |
I think that exposing defaults is simpler in terms of implementation and gives more control to the user. |
node-resolve
Feature Use Case
I want to be able to add
.ts
and.tsx
extensions when using TypeScript but I have to manually repeat default values which adds up unnecessary manual work. If the defaults were exported, I could reuse them easily.This would function similarly to
const { defaults } = require('jest-config')
.I can create a PR if you want.
Feature Proposal
Add
export
keyword toplugins/packages/node-resolve/src/index.js
Line 20 in cabe710
The text was updated successfully, but these errors were encountered: