Sebastien

@xjsender I would like to reopen this issue because there are multiple changes after metadata API 37 (in picklist per exemple) and I do not want to switch api version...

Hi @Patlatus ! Yep you nailed it, you will have to calculate them on your own, ChartJs will not does that for you. As explained in the link you found,...

I think this version is more elegant and cleaner. [gulp-jsforce-deploy.js.txt](https://github.com/jsforce/gulp-jsforce-deploy/files/908235/gulp-jsforce-deploy.js.txt) You can use it in gulpfile this way: ` gulp.task('deploy', cb => { return gulp.src('./src/**') .pipe(zip('pkg.zip')) .pipe(forceDeploy(options)) .pipe(rename(DEPLOY_RESULT_FILE)) .pipe(gulp.dest('.')); });...

What needs to be done for this PR to move forward ? What should I do ? @mojavelinux @jcubic

Ok then maybe we are fine with the actual implementation ? I'm ok to close this PR without merging it

@mojavelinux in the last version I let webpack use browserify to generate `path` dependency. I removed the tests that are checking for cases outside the `join` classic implementation and let...

> That seems reasonable to me. What should I do to make this PR move forward ? @jcubic @mojavelinux

I agree with you @mojavelinux, the title should be changed and your suggestion fits perfectly. I'll change the title Thank you guys for your help and time 🙏

Hi @zFitness I also experienced slow performance with huge repository. After profiling the lib with my implementation it seemed the issue was located inside a small function massively called. The...

Nice, it probably means your use case was not dependent to the fix. Cache works pretty well for you !