Michael Turkeev
Michael Turkeev
@zkat is something blocking this pr from merging now?
I think you can't. Not via options anyway. If you could though it would be in `spritesmithOptions`. You can split your set of source images though, and create multiple instances...
Wrap your template in a closure I guess? ```js const templateFunction = prefix => data => { console.log(data.sprites[0].image); var shared = `@mixin sprite_${prefix} { background-image: url(I); background-size: SWpx SHpx; }`...
What is the expected behaviour? Do you think I should make this configurable?
Ok, I'll try to migrate to chokidar. Thx for suggestion.
Actually chokidar is gone from dependencies in watchpack. So there probably will be no chokidar in webpack@5. Yet I'll try anyway.
`npm audit fix` should help. I can raise minimum required version for spritesheet-templates but it won't help too much. At least one of the security issues, is only fixed in...
uh... I never saw anything like this. I think some other part of your pipeline is doing this. How do you load styles and png's in webpack?
When `~` is used in css in webpack it will be resolved "globally"-ish. Independent of where it is required from. With `~` you also need to use `resolve.modules`. It matters...
I don't think it is possible with this plugin. It is modeled after [gulp-spritesmith](https://github.com/twolfson/gulp.spritesmith) and it doesn't seem to support that. It will require different compilation strategy and different api...