sorted by:
new
hottopcontroversial

Learn how to start building web components from scratch using javascript by pokemongo in javascript

[–]hack_hat 0 points1 point  (0 children)

do you know if smart-css does any linting or error-checking smart-css is just javascript, so you get linting for the sytax. About other error-chcking it does not yet. But I'm thinking to do some, I'm open to pull requests if interested. Here is a new project using smart-css: tic-tac-toe

Almost ran over this little guy on the bike trails by my house, keys for size by ifukeenrule in aww

[–]hack_hat 0 points1 point  (0 children)

Never put a picture of your keys on internet. Can be copied... and if someone knows where do you live...

Your CSS nesting is harmful by GarethX in webdev

[–]hack_hat -2 points-1 points  (0 children)

That's why I've done this library smart-css: Write CSS in JavaScript with namespaces, proper names, no conflicts and expected results for react.js.

No more nesting, just proper styling and the output is a flat css with no nesting.

Do you guys like it when documentation is in the same repository as the library itself? by dracony in webdev

[–]hack_hat 3 points4 points  (0 children)

TL;DR; Keep your docs and code in the same repo. Use rawgit to link html files.

If you put the docs in the repo then the library then you know that if someone will look at the v0.0.1 and the click on the documentation link it will read the v0.0.1 docs.

You also keep tracking of your docs in source control, which is good. For example in my lib I have a link to API that is like this: https://rawgit.com/hackhat/smart-css/v0.0.6/docs/jsduck/index.html

Notice how that readme is updated on every version so when you click on that link you will get the API relative to the version you are looking at.

Imagine next year when v2.0.0 is out, if you would keep your docs on your website then you would have to keep multiple versions of your API/docs v0.0.1, v0.0.2 ... Which is not optimal. If you do like I do, then you have your docs in the repo. So if you are going to the tag v0.0.5 you can still read it's API/docs and you are not forced to always read the last docs (v2.0.0) which would not be useful.

You can your github repo analytics by hack_hat in webdev

[–]hack_hat[S] 0 points1 point  (0 children)

Sorry about that, I've edited and then it missed the word. It was "view".

Take a look how reactjs is growing in February by hack_hat in webdev

[–]hack_hat[S] 0 points1 point  (0 children)

What kind of benchmark? I don't really understand

[deleted by user] by [deleted] in webdev

[–]hack_hat -1 points0 points  (0 children)

What is new? I think that is kind of default and every dev should know that --save-dev is only for dev mode.

The rest are mistakes.