digitalthrive / harvest Goto Github PK

i revice this Message when try install packages ->npm WARN package.json [email protected] No repository field.

i try change the package.json for bower.json and revice the messages -> bower browser-sync#^2.9.11 ENOTFOUND Package browser-sync not found and ->bower gulp-concat#^2.6.0 ENOTFOUND Package gulp-concat not found

well, i tried doing the manual installation, but the result is equal.

https://github.com/sindresorhus/gulp-autoprefixer

Quote from email:

I noticed that updating SCSS files in my project yielded errors and changes didn't show up in browser till relaunching gulp. Suspecting a issue specific to my particular project, I cloned Harvest elsewhere, did npm install then gulp to start afresh and tried to modify a SCSS file, and I got the same errors which means the problem is inherent to Harvest out of the box.

Worked fine locally, going to setup on a VM or on my Bootcamp to see if I can replicate.

After running the command gulp it throws me the error attached in the screenshot. Could you help with this..?

Great job! Thanks for sharing!

https://github.com/ryanbenson/Harvest/blob/master/app/styles/scss/config/_mixins.scss#L84

First of all, love the boilerplate - 10 times faster than the one I'm currently using. Great work!

I use a lot of @includes in my templates for headers/footer an such. For that I'd need the index file to be .php format. Just wondering what's the best way to go about altering the gulpfile for this and for browsersync to serve these files to the localhost?

Or...is there a better way to include html files, in html files that I don't know about?

Thanks :)

It would be nice if there was a quick way to switch to using less instead of scss.

Out of sheer laziness, more than anything - to let me (and others) be even more lazy by kickstarting a project with "npm harvest" or so instead of looking up the repo every time. Just a thought. Thanks for all your work!

Would be great if we could add a JSHint task and a task to compile a vendor bundle into a separate JS file.
Also, I don't see why you would want to uglify the javascript in your dev tasks.
And is there a reason why you write the css files to the src directory and not dist?

Sorry, I should have just asked a bunch of questions instead of raising a ticket :-)

gulp.task('scripts-vendor', function() {
    return gulp.src(['app/scripts/vendor/**/*.js'])
        .pipe(plumber())
        .pipe(concat('vendor.js'))
        .on('error', gutil.log)
        .pipe(gulp.dest('app/scripts'))
        .pipe(browserSync.reload({stream: true}));
});


gulp.task('scripts-vendor-deploy', function() {
    return gulp.src(['app/scripts/vendor/**/*.js'])
        .pipe(plumber())
        .pipe(concat('vendor.min.js'))
        .pipe(uglify())
        .pipe(gulp.dest('dist/scripts'));
});

it's almost not worth mentioning :) but gulp-connect is no longer a devDependency, package.json, line 11

furthermore, excellent repo!!

link to documentation is dead - http://www.ryanbensonmedia.com/documentation

Hey! Thanks so much for this boilerplate, just started using it recently and love it.

Except when having an scss error ;) (in my case, forgetting a semicolon)

When I fix the error, gulp does compile the scss files anymore. I have to restart gulp in order for it to work again. It still does other tasks though, just the scss one crashes I guess.

Something in app/scripts/src/main.js might try to utilize /app/scripts/src/_includes/jquery, which will fail due to wrong concat order.

Unless there is an Harvest way to do this, that I am missing here I would suggest this quick fix to put everything in /_includes before anything else, like so: https://github.com/quakenul/Harvest/blob/master/gulpfile.js

So... a bit OT but you know...

Hi,

Just need to note to update gulpfile.js file related to Gulp from v3 to v4. As Gulp v3 is incompatible with Node v11+ which shows following issues.

ReferenceError: primordials is not defined

This can be solve in following ways.

1. Upgrade gulp to v4 . This Solution Will Solve Your Error.
2. To downgrade Node to v11 by keeping gulp to v3, To Solve This Error.
3. To pin graceful-fs to version 4.2.2 that’s known to work under Node v12 by keeping gulp to v3.

To apply 3rd Option, follow are the changes needed.

1. Remove Node_Modules folder from your working directory.
2. Create an npm-shrinkwrap.json file beside of package.json file.
3. Add following code in that file.
   { "dependencies": { "graceful-fs": { "version": "4.2.2" } } }
4. Now just run npm install

This will solve it.