Use NodeErrorOptions directly from the postcss types - #133
Conversation
realityking
commented
Mar 30, 2021
Tests are failing all over. This must be related to the PostCSS bump. |
shellscape
commented
Mar 30, 2021
Looks like snapshots out of date due to the version bump. Some additions and removals from the shape of return objects. You'll have to go over each one individually, but from the few I looked at it looks like it's safe to update the snapshots. |
realityking
commented
Mar 31, 2021
Will do. Do you use some tool to generate the snapshots or is that a manual process? |
realityking
commented
Apr 5, 2021
@shellscape Can you give me a hint how the snapshots are created? Thanks! |
This requires at least postcss 2.8.9
realityking
commented
Apr 5, 2021
Thanks! That worked :) I had a look through the snapshots and I don't think I can review them. The changes have accumulated over multiple PostCSS versions and I don't know enough about the inner workings of PostCSS. What I could do, it submit a number of smaller PRs that would have smaller, more isolated changes to the snapshots. What do you think? |
shellscape
commented
Apr 6, 2021
I think you're letting the size of a diff overwhelm you a bit. The differences in the snapshots are almost exclusively around internal |
realityking
commented
Apr 8, 2021
You're not wrong about the size 😄 But it's compounded by the fact I'm not that familiar with the interface of PostCSS. I'd be happy to break it into smaller upgrades that I'd be more comfortable reviewing. Let me know if you wanna do that. |
shellscape
commented
Apr 9, 2021
realityking
commented
Apr 9, 2021
Thanks for taking a look & all the best for your kids 🙂 |
joscha
commented
Apr 27, 2021
@shellscape any chance we could get a new release with this change? Cheers! |

A quick follow-up to #132. postcss/postcss#1549 was merged very quickly so now
NodeErrorOptionscan be referenced without a deep import.This includes the required upgrade to PostCSS 2.8.9 that includes the above fix.