Yarn & NPM not pulling latest version
splicebison opened this issue · 6 comments
When using yarn add, I get v4.3.1 however the code is outdated somehow. I've tried multiple node/npm/yarn versions as well as clearing yarn cache. I need the newer version of gulpfile.js > tasks > browserSync.js to inject the connect-history-api-fallback into the new extraMiddlewares prop provided in the latest version. Any thoughts on this?
@splicebison thanks for submitting. how do you know the code is outdated, or what makes you believe it is?
@benjtinsley Viewing file node_modules > blendid > gulpfile.js > tasks > browserSync.js.
@splicebison ah i understand. it appears that particular change has not been rolled into a release yet. we are working on one sometime this week, i will keep you posted when it goes up
Ok, please do let me now. I'm using the Raw file pasted into the node_module at the moment in anticipation (time constraints). Thanks.
I just did:
$ mkdir /tmp/blendid-test && cd /tmp/blendid-test
$ yarn init -y
$ yarn add --dev blendid
$ grep version node_modules/blendid/package.json
"version": "4.4.1",
The node_modules > blendid > gulpfile.js > tasks > browserSync.js
seems ok also. Resolved?
@maoueh Tested and working. Latest 4.4.1 pulls correct files. Thanks. Closing issue.