You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The example Webpack / Rollup config linked to in the bundling section of the installation page will only work for an NPM based project, not Yarn or any other PnP / monorepo setup.
The Webpack config can be made to work with any setup that correctly modifies the resolver by changing the line
(see this note in the CopyWebpackPlugin docs) This relies on the "showlace.js" file exported in Showlace's package.json being in the same directory as the "assets" folder which seems a bit messy but I could not find a better way since you cannot "resolve" a folder in CommonJS.
I have never used Rollup so I am not sure what the best way to achieve the same in Rollup would be. Perhaps someone more familiar can advise.
Alternatively we could add a mention in the Shoelace documentation or as a comment in the config files that this is something to consider when not installing with NPM.
Happy to do a PR on the Webpack example repo with this change if that is the agreed solution.
The text was updated successfully, but these errors were encountered:
Describe the bug
The example Webpack / Rollup config linked to in the bundling section of the installation page will only work for an NPM based project, not Yarn or any other PnP / monorepo setup.
The Webpack config can be made to work with any setup that correctly modifies the resolver by changing the line
to
(see this note in the CopyWebpackPlugin docs) This relies on the "showlace.js" file exported in Showlace's package.json being in the same directory as the "assets" folder which seems a bit messy but I could not find a better way since you cannot "resolve" a folder in CommonJS.
I have never used Rollup so I am not sure what the best way to achieve the same in Rollup would be. Perhaps someone more familiar can advise.
Alternatively we could add a mention in the Shoelace documentation or as a comment in the config files that this is something to consider when not installing with NPM.
Happy to do a PR on the Webpack example repo with this change if that is the agreed solution.
The text was updated successfully, but these errors were encountered: