4 ms·

I think the trend of front-end projects not providing a compiled `dist` folder with the assets for web inclusion to be a bad idea. This requires me to NPM insta

I think the trend of front-end projects not providing a compiled `dist` folder with the assets for web inclusion to be a bad idea. This requires me to NPM install this "front-end code" (no Bower) and then add this Gulp compilation to my build. What happened to adding a `dist/hack.min.css`? Why no Bower?

insin 10y ago
The README contains a link to the built version on npmcdn: http://npmcdn.com/hack http://npmcdn.com/hack
- mikegioia 10y ago
  Yea, but how does that help me in my dev projects? The nice thing about Bower/NPM is that you can pull repos at specific versions or pull in new versions of a project. Adding a line to my build script to include a file at (say) `./vendor/hackcss/dist/hack.min.css` is a lot easier than having to run his Gulp compilation script. CURLing or including this public link isn't really an option :/
  - insin 10y ago
    Then I didn't understand the complaint, as this does include a dist/ folder in the npm package (which is also what npmcdn uses), so you'd just npm install it as normal :)
    - mikegioia 10y ago
      Oh I see what you mean. I didn't know that NPM added a dist folder when you install it that way.
      - kylestlb 10y ago
        Yes, when you publish an NPM package it grabs anything not ignored by .npmignore or .gitignore, which can include css, a dist folder, etc., quite useful!
  - krastanov 10y ago
    Would that not pollute the git history of the project with "junk" diffs of the compiled min.css file? I can see people not wanting to do that on principle. But yeah, I would really like a way for the builds to be available in the way you describe without any git history issues.