Jovica Aleksic
Jovica Aleksic
Or you could manually init dotenv pointing to electron-builder.env in your entry or webpack config file?
Okay I found a working solution - but only for `scss` files.. Turns out that `sass-loader` supports variables, which `css-loader` doesn't (not sure about `less-loader`) It works in development and...
I guess a "proper" solution would be using postcss. Will investigate.
@develar I think the sass support as shown in my screenie up there is good enough and should be implemented. It simply provides a `$__static` variable to all processed sass...
> I've fixed it this way, no patching required: > > 1. Add the following to your webpack configuration: > > ```js > { > resolve: { > alias: {...
Actually, I'd go one step further: I suggest we provide this alias out-of-the-box in the first place! @develar Any objections? Currently, we have the `@` and the `common` aliases. It...
https://github.com/loopmode/electron-webpack-static-examples
I can't say what exactly is missing, but normally, there is much more config generated by electron-webpack. In your config module, export a function instead of an object. That function...
Shot in the dark, gut feeling: Are you importing a css file from node_modules from within your App.css? If so, don't do it. Instead, import it from your App module...
I think we still have lots to improve in the docs. Meanwhile: https://github.com/loopmode/electron-webpack-static-examples