jr-cologne/gulp-starter-kit

A simple Gulp 4 Starter Kit for modern web development.

gulp-starter-kit's Issues

Task Sass not watching scss partials.

Changes only applies when save main scss file.
Other files with underscore (_partials.scss) not watching.

Installation in current directory: src folder missing, wrong installation confirmation message

Describe the bug
The following is broken regarding the installation in the current directory via the --current-dir flag:

• the src folder is not copied over
• after installation finished, the following message is displayed: Your project has been set up to the folder.

To Reproduce
Steps to reproduce the behavior:

1. Create new (empty) directory (mkdir test)
2. Change to created directory (cd test)
3. Installation via npm init @jr-cologne/gulp-starter-kit test --current-dir

Expected behavior
The following is expected to happen:

• the src folder should exists including the default source files
• after installation finished, a message like Your project has been set up to the current folder. should appear

rtl direction

Is there is a way to export two direction per page?
Just like
index-ar.html
index-en.html

Use incremental builds for better performance

I just learned there is this Gulp feature called incremental builds which lets you filter out unchanged files so that they are not unnecessarily processed by the build system.

use scss

Its possible add the scss options instead sass ?
Thanks you

First stable version

Hi everyone,

I am aiming to release the first stable version of this Gulp Starter Kit by July/August this year at the latest.

In order to achieve a version which is very comfortable to use and also reflects the needs of your projects as good as possible, I am now asking for your suggestions and feature requests.

I really appreciate any ideas for potential improvements and would be happy to discuss them with you. So, feel free to comment on this issue!

In case you don't really have own ideas, here's a list of features and improvements I am already considering to implement:

• support of HTML templating languages like Pug (first implementation: #19)
• support of more CSS preprocessors (e.g. Less, Stylus) (first implementation: #21)
• better directory structure for Pug: (implemented: #20)

  src/pug/
    partials/_header.pug, _footer.pug
    helpers/_mixins.pug
    templates/_default.pug
    index.pug
  

• option to convert images to webp (not before beta)
• use incremental builds for better build performance (implemented: #25)
• CLI improvements:
  • configuration options for installation process (e.g. choosing the CSS preprocessor)
  • improvements regarding the UX and UI of the CLI (e.g. better visualization with chalk and ora)

Please let me know what you think about the current list as well.

Thank you all in advance!

Best regards,
@jr-cologne

Build after each change

I noticed that during any change, the dist folder is built from scratch, which means that all images are also minified.
Could you add a production and development version? I tried but unfortunately it did not work out. Thanks!

Update dependencies

The following dependencies specified in package.json need to be manually checked and updated to the next major version.

• gulp-autoprefixer
• gulp-babel
• gulp-imagemin

scss files not gulping on save

I couldn't figure out why it wouldn't gulp the .scss files when I saved the file. You had to save the main .sass file for it to gulp.

The .scss files will not gulp because the destination has no folder scss, this need to change to sass

src_assets_folder + "scss/**/*.scss",

replace with

src_assets_folder + "sass/**/*.scss",

Autoprefixer doesen't work

Do not use latest versions published on npm!

The currently recommended version is v0.5.0-alpha.
Please do not use the latest versions (v0.6.0-alpha+) on npm since they're broken.

This means, the current installation command using npm init looks like the following:

npm init @jr-cologne/[email protected] your-project-name

Update: Since the latest version is now v0.5.1-alpha as I published a small patch, you don't longer have to specify the exact version number when installing the Gulp Starter Kit.

Update: I just deprecated the versions v0.6.0-alpha to v0.6.4-alpha on npm. Because there now is a functioning latest version as well as a deprecation warning, I am going to close this issue.

Replace Autoprefixer browsers option to Browserslist config

Use browserslist key in package.json instead of specifying browsers through autoprefixer options.

npm init installation is not working

The installation which uses the command npm init is not working as expected.

The command npm init @jr-cologne/gulp-starter-kit produces something like the following output:

command not found: create-gulp-starter-kit

I guess I need to introduce some kind of installation script called create-gulp-starter-kit.

Unfortunately, I am definitely not familiar with this. If somebody knows what to do, feel free to help me out. I would really appreciate any sort of help.

Add support for images

Support installation in current working directory

Add support to install the Gulp Starter Kit in the current working directory.

The installation command should look like this:

npm init @jr-cologne/gulp-starter-kit your-project-name --current-dir

When installing in an already existing directory, we should make sure not to overwrite existing folders and files, e.g. src and .editorconfig.

Better clarify supported node versions

Hi there, dear Hacktoberfest contributors,

it would be good if we could better clarify which node versions are supported by this Gulp Starter Kit.

I think, it would be enough to add a more specific description of our requirements with regards to Node.js to our README file. But, in case you've any better ideas how to better clarify supported node versions, feel free to suggest them.

Here's a quick list about what is involved in this issue:

• Comment here to let others know you would like to take this issue
• Follow our quick contributing guide starting from step 2
• Check out the required node versions of the project's dependencies
• Consider v8+ as the requirement, but make sure all dependencies match this requirement
• Make your changes to the documentation to inform users about our supported node versions

All right, have fun and celebrate Hacktoberfest with us! 🎉

Thank you very much in advance, I really appreciate your contribution!

Best regards,
@jr-cologne

Replace gulp-cssnano with gulp-clean-css

I just found out that the dependency gulp-cssnano for minifying CSS seems to be deprecated or is at least no longer maintained.
As a consequence, I would replace this with gulp-clean-css.