feat(ie11): add ie11 to build

[redallen]

Use existing conversion utilities to write patternfly-ie.css which contains all components + base styles.

Closes patternfly/patternfly-react#2092

[patternfly-build]

Deploy preview for pf-next ready!

Built with commit 4d74198

https://deploy-preview-1876--pf-next.netlify.com

[seanforyou23]

Looks like the glob pattern isn't working. Locally I'm getting the following

Is getStylesheetPaths returning a proper array for you? Looking into it..

[seanforyou23]

Actually just realized I hadn't built patternfly yet, which I suppose others may also do when developing locally. Could we add something like the following to getStylesheetPaths? You could add it right before we work with the files.

if (files.length === 0) {
  throw new Error(`getStylesheetPaths didn't receive any stylesheets to parse`);
}

[seanforyou23]

It would also probably also be a good time to fix the copy/pasta in the doc, and use something like /Path/to/patternfly-next/dist/{components,layouts,utilities}/**/*.css instead.

[seanforyou23]

So the main problem I see now is that when an instance of undefined is encountered, the script doesn't inform the user of where. The resulting stylesheet just contains Error: Stylesheet contains undefined.

What I'd think to do here is first produce the problematic file and after that throw the error. This way users can search the resulting file to get a clue as to what went wrong.

Also, we probably want to handle the error better?

[seanforyou23]

Nice work!

[patternfly-build]

🎉 This PR is included in version 2.10.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀