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
At the risk of looking like an idiot, I'll say it.
I suggest you mention in your documentation an example of how to specify the path to the "binary" for Windows users. I think Linux users and maybe Mac users throw around the term "binaries" a lot and assume everyone knows what they are talking about.
Being primarily a Windows user, what could have saved me like... 1.5 days of time... was if your documentation had an example of how to point to the Yuglify "binary" in the PIPELINE dictionary.
I went down the rabbit hole of messing with folder permissions, I tried putting Yuglify in every directory imaginable, I disabled my UAC on my OS... and in the end, it seems so obvious now. I don't know why your default for YUGLIFY_BINARY is '/usr/bin/env yuglify' (why the space?) but to Windows users, this is unfamiliar. I guess that's how you open programs on Linux. Sure, cool little knowledge nugget there, and maybe that will come in handy when I go to deploy...
But when I just want to get started and use a package to see if it's going to work... and Yuglify is the default... and I don't deeply know npm or Javascript best-practices (working on it!), I think your docs could be more clear.
My 10 cents.
The text was updated successfully, but these errors were encountered:
The syntax used in the documentation /usr/bin/env yuglify this referer to virtualenv which you can use on both Linux and Windows. Virtual environments bring a certain number of advantages, I advise you to look at what it is to understand.
If you really want the easier solution, you should have been to use css-html-js-minify compressor, which is based on python package and doesn't require anything more than pip install.
Don't hesitate to tell me if you have questions.
Buky
At the risk of looking like an idiot, I'll say it.
I suggest you mention in your documentation an example of how to specify the path to the "binary" for Windows users. I think Linux users and maybe Mac users throw around the term "binaries" a lot and assume everyone knows what they are talking about.
Being primarily a Windows user, what could have saved me like... 1.5 days of time... was if your documentation had an example of how to point to the Yuglify "binary" in the
PIPELINE
dictionary.Link to the documentation I'm talking about.
If only you had said:
I went down the rabbit hole of messing with folder permissions, I tried putting Yuglify in every directory imaginable, I disabled my UAC on my OS... and in the end, it seems so obvious now. I don't know why your default for
YUGLIFY_BINARY
is '/usr/bin/env yuglify' (why the space?) but to Windows users, this is unfamiliar. I guess that's how you open programs on Linux. Sure, cool little knowledge nugget there, and maybe that will come in handy when I go to deploy...But when I just want to get started and use a package to see if it's going to work... and Yuglify is the default... and I don't deeply know npm or Javascript best-practices (working on it!), I think your docs could be more clear.
My 10 cents.
The text was updated successfully, but these errors were encountered: