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

Fixing postcss error: newer versions seem to have a "Syntax Error: name #669

Merged
merged 2 commits into from
Nov 20, 2019

Conversation

weaverryan
Copy link
Member

When enabling PostCSS, but not having a PostCSS config file, we attempt to catch the error so we can print out an example PostCSS file. In a project I just started, this was not happening. It appears that the e.name was SyntaxError. Since we're already looking for a very specific error message, I think the name was overkill anyway (though I did check for e.message just as an extra sanity check).

Copy link
Collaborator

@Lyrkan Lyrkan left a comment

Choose a reason for hiding this comment

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

AppVeyor failure is weird but definitely not related to the PR.

It also makes me wonder why we have lodash in our dependencies, it doesn't seem needed at all.

@Lyrkan
Copy link
Collaborator

Lyrkan commented Nov 17, 2019

It also makes me wonder why we have lodash in our dependencies, it doesn't seem needed at all.

Found out why: it was needed when we embedded a patched version of the webpack-manifest-plugin.

We could probably remove it safely now and also move fs-extra to devDependencies.

@weaverryan
Copy link
Member Author

Nice research! I did both things - tests pass locally, let's see how if the CI is happy :)

@weaverryan weaverryan merged commit 8116e18 into master Nov 20, 2019
@stof stof deleted the weaverryan-patch-1 branch November 20, 2019 11:17
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