Skip to content
This repository was archived by the owner on Dec 19, 2024. It is now read-only.

"Cannot read property '_autoprefixerDisabled' of undefined'" #47

Closed
miketaylr opened this issue Nov 13, 2014 · 11 comments
Closed

"Cannot read property '_autoprefixerDisabled' of undefined'" #47

miketaylr opened this issue Nov 13, 2014 · 11 comments

Comments

@miketaylr
Copy link

I originally filed this over at webcompat/webcompat.com#394.

I used to have:

├─┬ grunt-cssnext@0.1.1
│ ├─┬ cssnext@0.2.3
│ │ ├─┬ autoprefixer-core@3.1.2

Deleting node_modules and reinstalling I now have:

├─┬ grunt-cssnext@0.1.1
│ ├─┬ cssnext@0.2.3
│ │ ├─┬ autoprefixer-core@3.2.0

And now grunt cssnext fails with "Cannot read property '_autoprefixerDisabled' of undefined'"

@miketaylr
Copy link
Author

This solves my issue:

rm -rf node_modules/
npm install autoprefixer-core@3.1.2
npm install
grunt

Now the task succeeds.

@Macxim
Copy link
Contributor

Macxim commented Nov 13, 2014

Same here with gulp-cssnext.
Complete error is here.

@MoOx
Copy link
Owner

MoOx commented Nov 13, 2014

Autoprefixer takes a risk by upgrading to postcss 3 as a minor release (3.1 ->3.2) (poke @ai). This kind of situation doesnt really respect semver :/
Anyway, I'll release tomorrow morning cssnext 0.5 and will bump all plugins at the same time.
I hope this will probably fix this issue.
Fixing autoprefixer version is the only workaround possible for now.=

@Macxim
Copy link
Contributor

Macxim commented Nov 13, 2014

Thank you very much for your speedy reply!

@ai
Copy link

ai commented Nov 13, 2014

@MoOx yeap, I should released 4.0 :). But I understand it only after release :(.

@ai
Copy link

ai commented Nov 14, 2014

@MoOx I unpublish 3.2 and release semver correct 4.0 release. Sorry. https://github.com/postcss/autoprefixer/releases/tag/4.0.0

@MoOx
Copy link
Owner

MoOx commented Nov 14, 2014

Good. Thanks !
Anyway, cssnext 0.5 is out.
Updating plugins right now :)

@MoOx MoOx closed this as completed Nov 14, 2014
@magsout
Copy link
Contributor

magsout commented Nov 14, 2014

👍 thanks @MoOx

@Macxim
Copy link
Contributor

Macxim commented Nov 14, 2014

Efficiency at its best. 👌

@miketaylr
Copy link
Author

Whoa, fixed while I was sleeping. :)~

@mymai91
Copy link

mymai91 commented Mar 19, 2015

Good solution. Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants