Webpack loader support

[lijunle]

From @lijunle on September 19, 2015 21:20

Webpack loaders are a special way to "load" code into webpack.

There are two syntax to use webpack loader:

• Via require function
• Via webpack config file

Copied from original issue: lijunle#14

---

There are several syntaxes about Webpack loaders:

• The require calls. (example) [3]
• CLI --module-bind options. (example) [2]
• Configuration properties.
  • Single loader in module.loaders.loader string (example) [1]
  • Multiple loaders concatenated with ! in module.loaders.loader string (example) [1]
  • Multiple loaders in module.loaders.loaders array (example) [1]
  • Loader with queries in module.loaders.loader string (example) [1]

Other considerations about loader:

• Configuration file requires other module or references global variables. [2]
• Loader can be used in module.loaders, module.preLoaders and module.postLoaders [1]
• Configuration will be set inside node.js API call. (example) [3]
• The configuration file can be specified from CLI via --config option. The default configuration file webpack.config.js will be leveraged if not specified. [2]
• It is possible to pass multiple configurations. [3]
• Loader naming convention is specified via resolveLoader.moduleTemplates setting in configuration file. Default is ["*-webpack-loader", "*-web-loader", "*-loader", "*"]. [2]

Notes:

• The items marked as [1] will be implemented and supported.
• The items marked as [2] will be supported with the default values. If someone request and provide his meaningful scenario, open an issue and let us how to support it.
• The items marked as [3] are considered as not supported. If you think they are necessary and have a good reason, please open an issue.

[lijunle]

From @js08 on October 21, 2015 16:3

@lijunle is the issue fixed

[lijunle]

No, not yet. I do not have full scenario to support this. If you have a project using webpack, then you can depcheck the project and resolve the webpack issues. I guess webpack might be complex because it use its naming convention to require packages.

[lijunle]

From @js08 on October 21, 2015 16:16

@lijunle to check webpack dependencies do I need to use special commands

[lijunle]

Let me clarify, webpack has many loaders, plugins, etc. There is a simple way to depend on one webpack loader/plugin (check this docs). Those usages do not follow require function call. We may need to some special way to detect them.

Currently, such special command does not exist.

If you want to work on this, read webpack's document and depcheck's pluggable design doc.

[lijunle]

From @js08 on October 21, 2015 17:12

@lijunle does this npm package https://github.com/dylang/npm-check supports webpack

[lijunle]

I don't think they support. Npm-check use depcheck to detect unused dependencies.

[lijunle]

From @js08 on October 21, 2015 17:21

@lijunle so are you not checking for packages in devDependencies which is mention in package.json

[lijunle]

@js08 I don't get your meaning, is that related to webpack issue? If not, please open another issue.

[lijunle]

From @js08 on October 21, 2015 18:4

@lijunle if npm-check packages supports webpack we can use the same code in depcheck-es6

[lijunle]

From @js08 on October 22, 2015 18:50

@lijunle can you tell what exactly is the issue its confusing

[lijunle]

From @js08 on October 23, 2015 14:6

@lijunle lijunle#27 if you look at this it seems you have closed

[lijunle]

From @js08 on October 26, 2015 14:19

@lijunle here is an example for todomvc app, can you fix it https://github.com/rackt/redux/blob/master/examples/todomvc/webpack.config.js#L22

[lijunle]

Hi, @js08

I am sorry to tell you that, I am not going to work on this issue. Because of the estimated complexity of this issue is high, and the benefit is not very high. I will not work on this issue until my another working project reach my bar.

However, if you have ideas on this, please go ahead to implement it. I am welcome for a PR.