Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementing SystemJSPublicPathWebpackPlugin. Resolves #12. #14

Merged
merged 3 commits into from
Nov 30, 2020

Conversation

joeldenning
Copy link
Owner

See #12


module.exports = {
plugins: [
new SystemJSPublicPathWebpackPlugin({
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My thought is we can add this to webpack-config-single-spa, and then remove the set-public-path.js files entirely from all the templates.

@joeldenning joeldenning merged commit 78308fc into master Nov 30, 2020
class SystemJSPublicPathWebpackPlugin {
constructor(options) {
this.options = options || {};
if (!isWebpack5 && !this.options.systemjsModuleName) {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to be a little more future-proof, could we do a check here for if it's >=5 or <5? otherwise we'll have issues when v6 is out

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i didn't want to bring in the full semver library - my understanding is that package.json version numbers don't even have to be numbers? Not sure if they have to start with numbers, either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants