-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update Grunt, remove unnecessary items from Gruntfile, register task 'default' #58
Conversation
Yep, I'm seeing that with #33 checked out as well. Will put a patch in this PR. |
@benlk Do you want help narrowing down what happened or do you have an idea? |
Assistance would be welcome. |
It's not WPBuddy/largo#1715 |
@joshdarby does this go away for you if in Appearance > CSS Variables you hit "Save Variables"? |
@benlk Sure does. |
Then it sounds like both of us had pre-Largo-0.6.4 CSS compiled, but since that isn't updated automatically when Largo updates (we require a human to push the button) we had to clear the old styles and generate new ones. It's not a problem with this PR or #33, or even this theme. (And WPBuddy/largo#1137 would solve the problem by getting rid of that cached stylesheet.) OK to merge? |
Awesome. 👍 |
Changes
This pull request makes the following changes:
package.lock
version
task, because we haven't been versioning this software for releasegrunt-contrib-pot
,grunt-confirm
,grunt-git
,grunt-po2mo
,grunt-pot
, andgrunt-version
as they're unused in this project. If we end up making this theme translatable, we should usegrunt-shell
as a wrapper for thewp i18n
tools.Why
This should clear up the npm-related security alerts for this repo, as well as bring improved syntax handling in LESS files for CSS'
calc()
.Testing/Questions
Features that this PR affects:
Questions that need to be answered before merging:
Steps to test this PR:
grunt
and watch for errors: there should be none, and thedefault
task should be run.