bag in new version - Githubissues

ease-space commented 5 years ago

Bag in new version 9.0.1. With old version 8.0.10 good work Снимок

montezume commented 5 years ago

We are having the same issue 🙏

jonathantneal commented 5 years ago

I’m sorry I can’t help you right now. The details are far too sparse for me to setup a repeatable bug. I know you didn’t mean to do that. I have done the exact same thing before, and I will again. It was good of you to report the issue. However, this issue will be closed very soon if no additional information is provided.

I know that’s not what you want to read. I would feel the same way. Please, let me explain:

Without additional details, I want to close this issue in order to help you resolve this issue. See, if this issue is not open and immediately visible, then other users may create new, similar issues with reproducible code that help me diagnose the cause the write the fix. This is why I request that you provide a reduced test case or a live example in CONTRIBUTING.md. The CONTRIBUTING.md appears for anyone opening new issues.

However, if I leave this issue open, and if other affected users see the original post — they may not take the time to check its details thoroughly. They’ll skim the issue enough to affirm that it matches their own experience, and then they will add some kind of “me too”. I know this because I’ve done it, too. And I know I’ll do it again. It’s so hard to know if I’m providing enough details when I’m frustrated and trying to get work done.

Unfortunately, the missing details don’t help help me, and it don’t help you, either. It’s actually kind of discouraging and distracting to know that there are problems I want to fix but can’t. And it’s discouraging to you if I don’t help you. I want to help you. I love helping you!

I know that it’s discouraging to you if I close this issue, too. I’m sorry about that.

Consider this — the best I can do with what you’ve given me is study the pictures, try to figure out how you are using PostCSS and PostCSS Custom Properties, and then copy the directories and file structure that I see in the pictures to try and recreate your circumstances. That’s tricky and time consuming, because most of the errors reference other projects. I don’t have the time to do all of that right now.

I really appreciate anyone who can setup a small project that reproduces this issue.

montezume commented 5 years ago

Sure, I can make a reproduction project in a little bit. Just need to finish up some other stuff first. 😄

jonathantneal commented 5 years ago

Thank you so much!

kevinansfield commented 5 years ago

I'm having the same issue. Code in question:

:root {
  --animation-speed-fast: 0.15s;
  --animation-speed-normal: 0.3s;
  --animation-speed-slow: 0.45s;
}

Error message:

postcss-custom-properties: <css input>:1:1: Unknown word
> 1 | 0.15s
    | ^

Unless this is invalid CSS it seems the issue may actually lie in the postcss-values-parser upgrade? Looking at the OPs screenshots it's failing at the same value format (0.2s)

kevinansfield commented 5 years ago

Related upstream issue here https://github.com/shellscape/postcss-values-parser/issues/76

kevinansfield commented 5 years ago

postcss-values-parser@3.0.5 fixes the s value suffix bug so a dependency update would close this issue.

jonathantneal commented 5 years ago

This has been published in 9.0.2 🎉

postcss / postcss-custom-properties

bag in new version #186