-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Stopped working since update 3.0.1 #122
Comments
Thanks for the issue! Do you have a problem when the option is enabled? |
Thank you for the quick reply! I've enabled
I tried installing an autoprefixer globally using |
Looks like a bug. I'll try to reproduce this on my machine. Most likely related to 7b09fa2 |
@ddawdler, Can you share your configuration of the plugin and file that has the problem? |
Sure, here's an example of the CSS I most often prefix with the extension:
It doesn't make much sense but I've gathered all properties in one place. On neither of my machines I don't do any additional configuration to the extension. I use it as it is right after installation. As for my files, they are simple CSS files. No post-processors, no webpack or anything like that. Before updating to version 3.0.1 running autoprefixer on the CSS mentioned above gave me this result:
On version 3.0.1 running the autoprefixer doesn't add any prefixes and does no changes to the styles. They are left as in the first example. If this is of any help, I'm running Windows 10 with updated VS Code. |
I'm having the same issue with the same error. Is it possible to downgrade the extension on my machine? |
Sure! To install the previous version, go to your extensions, click the little cog wheel icon on the Autoprefixer extension and choose "Install Another Version". I installed 3.0.0 and it works great on my machine. |
I am having the same issue. The downgrade suggested above — to 3.0.0 — was able to restore the functionality before the upgrade. macOS: 10.15.4 |
As I understand it, the problem applies to environments that do not have settings for autoprefixer. Looks like this is related to
Most likely this is related to With common settings this plugin works as expected: // Place your settings in this file to overwrite default and user settings.
{
"autoprefixer.options": {
"browsers": [
"last 4 versions",
"ie >= 9",
"> 5%"
]
}
} So, in this case, this is the correct behavior. Just add the settings for the |
I can confirm this fixes the issue. Thank you for explaining! :) |
Is it possible to use just "defaults" for the value in the "browsers" property? Or does the extension only work properly if you specify what browsers to target? |
I'm gonna sound like a total noob and say I still have no idea how to fix this: what settings do I need to change? I don't have in VS I tried to put the settings above in |
hey, thank you... for whatever reason it worked this time. if I can bother you more I have a question: I work solo so I don't have a lot of work-flow proper practices set up for me... I had to come up with my own, and they are probably wrong - I find compiling from sass and then autoprefixing, then beautifying and then minifying ... quite tedious... have you got a suggestion to streamlining/automatise these processes? sorry if it sound like a dumb question... and I realise this is not the platform. |
This actually worked, Thank you |
[Autoprefixer] "autoprefixer.options": { 1、npm i -D autoprefixer The error is still there, how can I fix it? THANKS! |
Since the last update (3.0.1) the extension doesn't work. I've tested on two different computers, and running the Autoprefix command doesn't seem to do anything. The file registers a change and can be saved, but nothing happens to the code. I can confirm that reverting to the previous version fixes the issue.
Please tell me if I can provide any more useful information. The Developer Tools console doesn't register anything.
The text was updated successfully, but these errors were encountered: