Let's update recipes!

[UlisesGascon]

Hi people! 👋

In the last release... we removed the support for Bower. Many recipes now are very outdated. What do you want to do? Let's discuss it!

• Current list 👀

[silvenon]

Update one by one, I'm afraid 😄

[silvenon]

Note: @UlisesGascon has updated this list to reflect the ongoing PRs

Let's create a checklist:

• Less docs(less): update recipe #767
• Nunjucks docs(nunjucks): update recipe #766
• Handlebars
• Pug docs(pug): update recipe for pug #765
• asset revisioning docs(recipes): update asset-revisioning #777
• AWS S3 deployment
• browserify
• CoffeeScript
• Compass · recipe removed in Remove compass recipe (deprecated) #776 because it's deprecated
• GitHub Pages docs(recipes): update gh-pages #778
• HTMLHint docs(recipes): update htmlhint #779
• Liquify
• Heroku
• React Router
• React
• Rsync deploy docs(recipes): update rsync-deploy #775
• Stylus

[jaysunwalter123]

Nunjucks... pleeeeeeeeease 🤓

[jaysunwalter123]

Ok, I've updated the gulpfile.js for Nunjucks integration. Where and how can I submit it?

[diegoarce]

Is it possible to prioritize the checklist and maybe try to update one per month or something like that. I would love to have the Handlebars recipe.

[f97-2308]

Yeah... Pug can't config on current version... Update it, please... :)))

[silvenon]

@jaysunwalter123 by opening a PR to modify docs/recipes/nunjucks.md. 🚀

[silvenon]

Sorry about not updating recipes, it's not a trivial process, I'll try to update a few soon, starting with Handlebars and Pug.

[ly4nhkiet]

please update liquifly, thanks

[GlebBigma]

Pug?

[silvenon]

@GlebBigma feel free to add feedback in #765.

[ilicmarko]

I am really happy that people are using these docs still. Therefore, I will put my time to update most (as much as I can).

[ilicmarko]

I started to look into updating the docs and gulp-liquify is not maintained at all. It has a the prototype pollution vuln from lodash. I don't see any other alternatives.

[yuvashrikarunakaran]

It seems like the project has dropped support for Bower, which was once a popular package manager for front-end dependencies. Since Bower is outdated, and many of your existing recipes are likely based on it, you now need to consider how to maintain or modernize your dependencies and project structure.

Here are a few points we could discuss to help decide how to proceed:

1. Migrating from Bower to Modern Tools
   NPM/Yarn: Most front-end projects now rely on NPM (Node Package Manager) or Yarn to manage their dependencies. These package managers offer many advantages, including broader support, easy integration, and built-in modern workflows like tree-shaking and bundling.
   Webpack/Parcel/Vite: If some of your recipes were relying on Bower components for module loading or bundling, you could replace them with more modern tools like Webpack, Parcel, or Vite.
   Updating Build Tools: Your gulp setup might still work, but it's important to ensure that any outdated gulp plugins or Bower components are replaced by equivalents that can be installed via NPM or Yarn.
2. Updating or Replacing Recipes
   Go through your list of outdated recipes and figure out which ones are still relevant. For the ones you want to keep, update them by swapping Bower dependencies with NPM versions.
   For example, if any old libraries were brought in via Bower (like jQuery, Bootstrap, etc.), they should now be pulled from NPM or Yarn instead.
3. Refactoring Recipes
   Some of your recipes may require code refactoring due to differences in how modern libraries are managed. This includes handling imports (ES modules) or ensuring compatibility with modern build systems.
   Check for any deprecated or unsupported packages that you’ve been relying on and find modern alternatives.
4. Remove Bower Configuration Files
   As part of this clean-up, you’ll want to remove any lingering Bower configuration files like bower.json or .bowerrc, along with any references to Bower in your build scripts (like gulp tasks that reference bower_components).
5. Plan for Legacy Support
   Are there any projects that still rely on Bower? You’ll need a plan to support them (possibly in a legacy branch) or guide them through migration. This will ensure that no one is left with broken builds.
6. Documentation Update
   As part of the transition, it’s crucial to update your project’s documentation to reflect the removal of Bower support. Make sure instructions for setting up dependencies now point to NPM/Yarn.