1/7/2024 0 Comments Favicon codekit![]() Now you should be able to run the command from the terminal that would save you a significant amount of time in the future. □ Pro tip: install using silent option, -silent or -s, because suppressed output could speed up the installation progress. SPRO is available as an npm module, and you could install it locally or globally. You could watch videos and learn how SPRO works. But if you are unlucky, don’t hesitate: most errors could be resolved within a few minutes by debugging the problem and updating individual configuration files. There is a good chance that Gulp tasks would work for you in the first attempt. The features include extracting Critical CSS, add BrowserSync for easier development, linting your HTML, Sass and JavaScript files, as well as adding sourcemaps and pug template engine. SPRO has a lot of features in one place, so you don’t forget to add something to your project. Gulp tasks would handle all files based on the configuration files in the gulpfile.js directory. Tasks that are defined in the SPRO could process your HTML, CSS, JavaScript, font, favicon, and graphics files. This directory could then contain your individual modules for tasks.” “Node’s module resolution allows you to replace your gulpfile.js file with a directory named gulpfile.js that contains an index.js file which is treated as a gulpfile.js. It would also prepare a command to install all dependencies based on your answers.īesides the main configuration file, SPRO would add Gulp task files and other configuration files in the gulpfile.js directory. When you answer all questions, SPRO will store information to the. Instead of manually tweaking the configuration file, I have built a command that would start a questionary about the project structure. Read more about the idea and possible problems that Starter Project package it is trying to solve in the introduction article from the last year. …why not have a single package that could be reused on various projects with a single configuration file that could be easily updated. Instead of copy-pasting code from one project to another, why not have a single package that could be reused on various projects with a single configuration file that could be easily updated. Starter Project is conceived as a boilerplate of the latest best practices packed in Gulp tasks. About SPROĪbout a year ago I started working on my side project, Starter Project. Switching to npm scripts is something to consider, though. I like the idea that every task could be isolated, and project files could be used as separated entities. “…if you are happy with your current build system and it accomplishes all that you need it to do, you can keep using it!”Īmongst other great build tools, like Grunt, Webpack, Parcel or even npm scripts, my favorite is Gulp because I am most familiar with this fantastic tool. In another excellent article Why npm scripts, Damon Bauer says it very nicely: Some developers prefer Parcel because it is fast and it just works (so they say), some developers like to write npm scripts to avoid new levels of the abstraction, and some developers like to use CodeKit or Makefiles, which I didn’t even know of before. There has been a great discussion about the build tools in the Frontend Developers Slack group (now deprecated, moved to Discord). □ SPRO is in its early stages, and every suggestion, feedback or help would be appreciated! Why Gulp It is very flexible, and it could save you a vast amount of time that you usually spend on configuring your project. ![]() SPRO aims to set up a perfect development environment by learning about your project architecture and then setting up Gulp tasks for all your needs. SPRO (pronounces /es-pro/), or Starter Project CLI, is the best starting point for your next project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |