Blendid init seems to not work correctly on latest version (4.4.1)
maoueh opened this issue · comments
$ mkdir /tmp/blendid-test && cd /tmp/blendid-test
$ yarn init -y
$ yarn add --dev blendid
# Note that in latest Yarn version, the `--` is not required, `README.md` should be updated
$ yarn run blendid -- init
yarn run v1.4.0
$ /private/tmp/blendid-test/node_modules/.bin/blendid init
[09:35:33] Working directory changed to /private/tmp/blendid-test/node_modules/blendid/gulpfile.js
[09:35:35] Using gulpfile /private/tmp/blendid-test/node_modules/blendid/gulpfile.js/index.js
[09:35:35] Starting 'init'...
[09:35:35] Generating default Blendid project files
To start the dev server:
yarn run blendid
[09:35:35] Finished 'init' after 16 ms
✨ Done in 3.05s.
$ ls
node_modules package.json yarn.lock
Not sure what's wrong however. Specific to my machine? If someone could try on their end, would be appreciated :)
High chances it's not related to the init
behavior problem described in this issue. Can you open a new issue?
i encountered this yesterday and seemingly related to gulp.dest
merge-streams
or something else entirely. i'll take a crack at this and hopefully have something soon, in the meantime @kferran 's solution is the best for anyone else with this problem: install version 4.3.1
to ensure your new projects succeed
@benjtinsley I confirm init
works again with 4.4.2
. But @kferran should confirm for his own use case as I really think his problem is unrelated to the init
problem. We will know soon :)
Still running into the same issue on my end after upgrading to version 4.4.2
.
http://prntscr.com/i2drtz
interesting. @kferran when you run yarn run blendid -- init
or yarn run blendid
you are doing so from the kferran\website\app\
directory? it is strange that it is looking for the package.json
file within node_modules\
yes what @maoueh said. i think we can track this better in its own issue
Moved the issue I am having to #532