Closed Guria closed 5 years ago
Current documentation states following way to define options:
module.exports = {
plugins: [
{
plugin: CracoLinariaPlugin,
options: {
// Linaria options
},
},
],
}
But this doesn't works since current version tries to get config
property of pluginOptions. Which is obviously undefined
in this case.
OK sorry, but I'm really struggling to understand the root issue here. Are you suggesting that (undefined || undefined || {}).config || {}
doesn't work in that it throws an error or something? What is the scenario in which this breaks? What is the expected result here and how does moving the (
help? I'm not seeing how.
({ someLinariaOption: true } || undefined || {}).config || {} // {}
{ someLinariaOption: true } || (undefined || {}).config || {} // { someLinariaOption: true }
:tada: This PR is included in version 1.1.2 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
I'm not understanding what this is fixing. Can you elaborate?