-
Notifications
You must be signed in to change notification settings - Fork 65
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
fails if you lack module.exports.tslint.configuration (if you put your tslint config in a separate file) #57
Comments
it doesnt seem to work for me..
|
By updating to versions 4.3.1 of tslint and 3.3.0 of tslint-loader the error ceases to exist. |
It needs Tslint 4.0+ and there is also a test case for no tslint configuration, does the bug still exist? |
Added explicit check for Tslint version in code and documentation. |
running into something similar, but only if I'm consuming typescript from within |
@wcarmon can you provide an example repository? |
We gave up on that approach and just run linting directly to avoid any of
these issues.
…On Apr 22, 2017 04:38, "Gábor Soós" ***@***.***> wrote:
@wcarmon <https://github.com/wcarmon> can you provide an example
repository?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#57 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHEEt30198kwzadSj1TR7nlm8_Jc80Ruks5rybx3gaJpZM4LHIg_>
.
|
this fails with tslint 3.15.x and tslint 4.0.x
// on 4.0.x
Module build failed: TypeError: Cannot read property 'findConfiguration' of undefined
at resolveOptions (.../node_modules/tslint-loader/index.js:28:63)
// on 3.15.x
Module build failed: TypeError: Cannot read property 'findConfiguration' of undefined
at resolveOptions (.../node_modules/tslint-loader/index.js:26:63)
Workaround is to have an empty configuration object in webpack.config.js
(at
module.exports.tslint.configuration
)The text was updated successfully, but these errors were encountered: