The use of hard coded paths can lead to issues in some environments (for example, when using yarn workspaces). Hard coding is also not a great idea, in general. Using the resolve package, a small change to the webpack.conf.js would avoid potential issues.
JS not my day job... so I don't fully understand the nuances of webpack so I'm not clear on whether that's a terrible idea?
I also had other issues because I make things too complicated for myself. The most confusion one involved SVG files. Using ['file-loader', 'html-loader'] to store the individual assets as files won't work. It causes the toolbar to emit the filenames which are then interpreted as HTML (and not properly formed <svg src=...>). I would have thought there would be a better way to handle conflicts like this across multiple packages.
The use of hard coded paths can lead to issues in some environments (for example, when using yarn workspaces). Hard coding is also not a great idea, in general. Using the resolve package, a small change to the webpack.conf.js would avoid potential issues.
Q: Why do you need an explicit
quill$
?Alternatively, wouldn't this also work?
JS not my day job... so I don't fully understand the nuances of webpack so I'm not clear on whether that's a terrible idea?
I also had other issues because I make things too complicated for myself. The most confusion one involved SVG files. Using
['file-loader', 'html-loader']
to store the individual assets as files won't work. It causes the toolbar to emit the filenames which are then interpreted as HTML (and not properly formed<svg src=...>
). I would have thought there would be a better way to handle conflicts like this across multiple packages.