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
Since we moved to a github pages deploy, it would make things easier to understand if the target "public" folder had no assets tracked in git (i.e. was git ignored) and all the assets under git control were in more clearly documented locations.
To make this work, we basically need to add to webpack a step to copy those assets to the public folder using something like the copy-webpack-plugin. Looks like we'd have to use something like v 4.6.0 with the current outdated node version used to build
Since we moved to a github pages deploy, it would make things easier to understand if the target "public" folder had no assets tracked in git (i.e. was git ignored) and all the assets under git control were in more clearly documented locations.
To make this work, we basically need to add to webpack a step to copy those assets to the public folder using something like the copy-webpack-plugin. Looks like we'd have to use something like v 4.6.0 with the current outdated node version used to build
https://v4.webpack.js.org/plugins/copy-webpack-plugin/
https://github.com/webpack-contrib/copy-webpack-plugin/tree/v4.6.0
The text was updated successfully, but these errors were encountered: