Port to webpack 3 and Upgrade Antwar

[bebraw]

Port site to webpack 3 and a new version of antwar that fixes a variety of bugs. What's left:

• fix <title> tags, none of which are populated
• fix introduction sidebar links
• fix activation of current page in sidebar (i.e. displaying anchors)
• fix mobile sidebar (pretty much empty for some reason, maybe due to title issue)
• fix terminated build issue (not sure what's going on there 😕)

Resolves #720 (once titles are fixed, remember to double check vote title)

[skipjack]

Ok so here’s what i’m seeing:

• <title> doesn’t look like it’s populated on any page
• introduction sidebar links are broken… clicking those just duplicates the section name (e.g. /concepts/concepts)
• activation of current page in sidebar is broken

Aside from those I'm not seeing anything else broken but i'll keep poking around. I can look into to the two sidebar issues but I'm not sure what to do about the titles. It would be great if we could put that one to bed and close out #720.

I restarted the build as well to see if anything fails -- the last one got terminated somehow.

[skipjack]

Ok updated the lead-in description with what's left to do... I fixed two issues with the normal sidebar and will now look into the mobile sidebar. Also working on simplifying the webpack config even more.

[skipjack]

Yeah so the issue with the SidebarMobile component is that the routing data changed and many titles are missing. Once we figure out what the solution is for title and children it should be an easy fix.

[bebraw]

I upgraded the setup to use webpack 3 and fixed titles. Can you check the mobile sidebar bit? Also that termination issue remains most likely (some way to debug is needed).

[skipjack]

@bebraw I'll pull, test, and try to resolve the mobile sidebar issue. I restarted the build just to see if that would help, but honestly I'm not really an expert when it comes to CI. Although I just checked the build and it seems to be moving past the initial stages now.

[skipjack]

> webpack.js.org@0.1.2 lint:links /home/travis/build/webpack/webpack.js.org
> hyperlink -r build/index.html | ./scripts/check-links.js
Guessing --root from input files: file:///home/travis/build/webpack/webpack.js.org/build/

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

The build has been terminated

Not really sure what's failing here, is it hyperlink? @bebraw the output directory is still called /build, right?

[skipjack]

@bebraw I'm unable to find the necessary data within section.all(). Only some top level pages come back none of which contain any child pages:

I'm also not seeing the titles populated:

Please advise... I did wipe my node_modules and re npm install everything after checking out to this branch.

[skipjack]

Submitted Banno/polymer-webpack-loader#63 to fix the last remaining issue. @pierreneter I'm going to do another pass over all this and see if there's anything else that needs fixing or can be cleaned up. Expect it to be merged by the end of this week (this weekend at the latest).

[pierreneter]

4e1beb9 related to: get-alex/alex#175

alex . -q :

alex CLI searches for files with a markdown or text extension when given directories (e.g., $ alex . will find readme.md and foo/bar/baz.txt). To prevent files from being found by alex, add an .alexignore file.

and

node_modules is ignored by default.

[skipjack]

Will do a final pass over this tonight and get it merged.

[skipjack]

Ok @pierreneter tested this out and everything seems good to go. I did just submit webpack-contrib/install-webpack-plugin#118 to fix a broken remote link but we don't necessarily have to wait on that to merge. Also seeing issues with Travis' network again but I restarted the build so we'll see what happens. Latest this goes in is tomorrow.

[skipjack]

Ran all tests locally which only ran fine aside from the broken link from webpack-contrib/install-webpack-plugin#118. Doesn't make sense to hold this merge up just for that though. If anything else comes up we can resolve in a separate PR.

@pierreneter I'll likely start working on #1519 soon, and will talk with @bebraw to try to simplify the antwar configuration even more. Will submit separate PRs for that and cc you.

[skipjack]

@pierreneter it's in 🎉

Thanks again for all of your work on finishing this off. It should definitely make it easier to keep pushing the repo forward in terms of build process and infrustructure. I will try to set up a discussion soon, maybe in slack or something, with those interested in the infrastructure of the site so we can make a solid plan.