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

feature: allow passing through custom options to resolve #79

Merged
merged 1 commit into from Jul 30, 2021

Conversation

markjm
Copy link
Contributor

@markjm markjm commented Jul 27, 2021

letting us pass our own options (via settings in .eslintrc.js allows us to override all of the settings specified in https://www.npmjs.com/package/resolve - not just the ones this project "knows" about. spreading these first will ensure that the settings this project knows about will still work/override as expected while letting others pass through.

@markjm
Copy link
Contributor Author

markjm commented Jul 27, 2021

Hi @JounQin please let me know if you have any questions or concerns about these changes. For some more info on our use case, we are using this to pass in a custom paths function and memoized isFiles to help resolve a lot of failed stat commands due to the layout of yarn workspaces node_modules

@JounQin
Copy link
Collaborator

JounQin commented Jul 28, 2021

Seems nice to have to me.

But this should be a feature, not fix IMO.

@markjm markjm changed the title fix: allow passing through custom options to resolve feature: allow passing through custom options to resolve Jul 28, 2021
@markjm
Copy link
Contributor Author

markjm commented Jul 28, 2021

Seems nice to have to me.

But this should be a feature, not fix IMO.

fair, I have fixed up the commit and commit message

@JounQin
Copy link
Collaborator

JounQin commented Jul 28, 2021

@markjm TsResolverOptions should be updated to extends SyncOpts at the same time.

src/index.ts Outdated Show resolved Hide resolved
@JounQin JounQin merged commit 34c94c8 into import-js:master Jul 30, 2021
@JounQin
Copy link
Collaborator

JounQin commented Jul 30, 2021

Thank you! @markjm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants