-
Notifications
You must be signed in to change notification settings - Fork 10
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
passing a custom publicPath breaks serialization #65
Comments
I don't think it ever supported custom publicPaths other than the default '/'. Though consideration was made for it within our 404 and index templates. But now that it's consolidated and available under the config, this feature is needed. |
but it's there in config.js? |
will look at as I / after working on #66 , which now makes the case easy to reproduce. Just compare having a custom greenwood.config.js // bueno
module.exports = {};
// no bueno
module.exports = {
publicPath: '/owen'
} and running $ yarn build
$ cat ./public/index.html and compare the output |
This seems to be the offending output: {
path: context.publicDir,
filename: '[name].[hash].bundle.js',
publicPath: '/' // config.publicPath
}, will serialize even when It seem the webpack output is the same in .greenwood/, so seems to be isolated to just the serialize part of the pipeline. |
Ok, seems to be related to the interplay between setting |
Did this get resolved yet? I don't see a PR for this issue. |
Still open. Was hoping getting #74 in first would help with debugging |
Type of Change
Summary
Passing a config with a custom
publicPath
doesn't result in a serialized HTML fileconfig
index.html
should be something like
Details
Serialization has regressed, likely when #53 was merged.
The text was updated successfully, but these errors were encountered: