import/no-webpack-loader-syntax rule too strict

[domtra]

Hi there, in #806 some useful new rule regarding imports were added for the standard v10.

Unfortunately, one rule was added that causes a lot of problems in many of our projects. That is rule import/no-webpack-loader-syntax. It prevents you from specifying loader options in an import or require statement.

While I agree that for general situation, the webpack config file should be the place to add loader configs, in some situation this is simply not possible, or rather a lot of unnecessary work. Also, using a loader config within import or require is an 'official' way, not deprecated or anything else.

The official docs for this rule state that it is a non-standard way to use import. However, importing a non js or json file without a bundler (webpack in this case) does not make any sense anyways.

At the moment using inline comments to disable the rule is the only way for us to continue using standard. This is not very feasible, either, but I really want to avoid having to ditch standard and moving to eslint instead.

What do you think? Do these points make sense to you? Is it possible to remove that rule again?

[ematipico]

You can add loader options inside your webpack config file. Can you not?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.