-
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
[demo / bug] inline optimization is broken on subsequent page load #495
[demo / bug] inline optimization is broken on subsequent page load #495
Conversation
e6fa2d4
to
d502a90
Compare
952e614
to
d2907bb
Compare
Ok, so following the first error at least (unexpected end of input) on expandRoute(path) {
let routeShelfListIndex = this.shelfList.findIndex(item => {
let expRoute = new RegExp(`^${path}$`);
return expRoute.test(item.route);
}); As can be seen, it looks like a new HTML document is getting loaded right in the middle of that regex in the minified and inlined code, which appears to be another full copy of the page's HTML? 😳 expandRoute(e){let t=this.shelfList.findIndex(t=>new RegExp(`^${e}<!DOCTYPE html><html lang="en" prefix="og:http://ogp.me/ns#"> |
The plot thickens... checked a couple more things
So, basically it must be isolated to what is happening in our rollup.config.js, but specifically in the inlining logic. Let me setup a test environment know that I've been able to narrow things down. I probably botched a regex or On an unrelated note, I'm not sure we actually need the
|
Dang, so I think this is the issue
Essentially, the Regex inside our source code is getting interpreted by Looks like there is workaround here So I guess would need to go through and check all usages of |
Ok. moved to an issue now that I can reproduce in a spec locally. |
Related Issue
related to #447, this is an example of the
inline
optimization setting. Click here for the simpler diff. This is a known broken issue since it works in the specs, but not with the GreenwoodScore seems about the same?
Network requests (not entirely everything is inlined, but most)
Lighthouse
On Navigation 😬
Summary of Changes
optimization
setting to inline in greenwood.config.js<base href="/">
to set consistent reference point for all JS / CSS file requests