Use inputValues as shortcut?

[Johannes Ewald]

I'm not sure if I understand the docs correctly, but shouldn't the json-loader try to read from inputValues first?

I'm using @okonet's yaml-loader which returns the parsed yaml as json string. After that the json-loader re-parses the string which is unnecessary.

[Andrey Okonetchnikov]

It's probably unnecessary to use json-loader in addition to yaml-loader since the output is pretty the same. I could adjust yaml-loader to return the native object. This will eliminate an additional parse and the plugin should be then listed in basic section. WYT @sokra?

[Tobias Koppers]

@jhnns Yes we can do this.

[Michael Ciniawsky]

@jhnns @okonet Is this still relevant somehow? 👀 Or can we close this 😛 ?

[Andrey Okonetchnikov]

@michael-ciniawsky it doesn't look like I've updated the yaml-loader. Please feel free to submit a PR or I could transfer the loader to webpack-contrib org if this is more desirable.

[Johannes Ewald]

We deprecated the inputValues property, so this can be closed.

@okonet Regarding the yaml-loader: It would be nice if the yaml-loader would just generate an object and pass it on. The json-loader can handle inputs that are no strings.

I think, transferring the yaml-loader to webpack-contrib makes sense since yaml is a popular file format 👍

[Andrey Okonetchnikov]

Hmm, @jhnns I got this then attempted to transfer it:

You don’t have the permission to create repositories on webpack-contrib

Can someone add me?

[Michael Ciniawsky]

Can someone add me?

cc @bebraw @d3viant0ne

[Juho Vepsäläinen]

I think @d3viant0ne can comment on the proper process. We've done it before with mixed results.