Dave Conway-Jones

have you tried upgrading ? does the layout capability still function ?

Ok a quick test shows that gulp no longer builds it even with version 0.5 ( something about singular glob scss file missing.) so not an easy upgrade for something...

hmm - removing jquery would be nice (moving to 1.x) - but any clues how to load that scss file via npm ?

We run it through gulp - so that did the sass thing to build the .min.css for us. We load all extra libs as dev deps and then gulp does...

currently the gulp function does this - happy to take advice to update ``` function gridstack() { gulp.src('node_modules/gridstack/dist/gridstack.min.css').pipe(gulp.dest('dist/css/')); gulp.src('node_modules/gridstack/dist/gridstack.jQueryUI.min.js').pipe(gulp.dest('dist/js/')); gulp.src('node_modules/gridstack/dist/gridstack.min.js').pipe(gulp.dest('dist/js/')); gulp.src('node_modules/gridstack/dist/gridstack.min.map').pipe(gulp.dest('dist/js/')); gulp.src('node_modules/lodash/lodash.min.js').pipe(gulp.dest('dist/js/')); return gulp.src('src/gridstack-extra.scss') .pipe(replace('$gridstack-columns: 12 !default;','$gridstack-columns: 30;')) .pipe(sass({outputStyle: 'compressed'}))...

Well in theory changes from 0.5 -> 0.6 should not really include breaking changes... so removing events is a bad idea... but yes if below version 1 they are allowed...

Most of the time they would be using 6 or so... maybe 9, 12 etc... but there is nothing to stop a user going larger if they wanted to... (indeed...

I thought it may be as I was trying to use setColumn... have now reverted to setGridWidth and it's still the same behaviour on 0.6.4 - Is ok on 0.5.5....

Sure - I'm still not sure how that helps anything. We need to serve those files up - so we need them in a place we know (our dist folder)....

Yes - managed to get out there for a trip while back. Drove up Highway 1 etc.. I can see your point re downloads... but getting our users to download...