You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 20, 2018. It is now read-only.
Running "useminPrepare:html" (useminPrepare) task Verifying property useminPrepare.html exists in config...OK Files: src/index.html -> html Options: dest="angular" Going through src/index.html to update the config Looking for build script HTML comment blocks Warning: Error: You are not supposed to mix deferred and non-deferred scripts in one block. Use --force to continue.
The text was updated successfully, but these errors were encountered:
Did you ever solve this? I'm having the same issue because I added defer to a couple of script declarations to improve my score on the Pagespeed tools from Google, but after adding defer keep getting the error (and --force skips the replacement of this element).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As you can see in README of https://github.com/VividCortex/angular-recaptcha I need to use
async defer
in my code but when I use the grunt task useminPrepare with this confmodule.exports = { html: ['src/index.html','src/material.html'], options: { dest: 'angular' } }
and with this general task
... gtx.alias('build:angular', [ 'recess:less', 'clean:angular', 'copy:libs', 'copy:angular', 'useminPrepare', 'concat:generated', 'cssmin:generated', 'uglify:generated', 'usemin', 'clean:tmp' ]); .....
I get this error message
Running "useminPrepare:html" (useminPrepare) task Verifying property useminPrepare.html exists in config...OK Files: src/index.html -> html Options: dest="angular" Going through src/index.html to update the config Looking for build script HTML comment blocks Warning: Error: You are not supposed to mix deferred and non-deferred scripts in one block. Use --force to continue.
The text was updated successfully, but these errors were encountered: