search

vigetlabs / blendid

A delicious blend of gulp tasks combined into a configurable asset pipeline and static site builder
MIT License
4.97k stars 683 forks source link

Blendid init seems to not work correctly on latest version (4.4.1) #527

Closed maoueh closed 6 years ago

maoueh commented 6 years ago 
$ 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 :)

kferran commented 6 years ago

Running into a similar issue when trying to run yarn run blendid. image

Issue seems to show up in version 4.4.0 as well. I reverted back to version 4.3.1

maoueh commented 6 years ago

High chances it's not related to the init behavior problem described in this issue. Can you open a new issue?

benjtinsley commented 6 years ago

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 commented 6 years ago

@maoueh @kferran i released 4.4.2 which addresses this. if you encounter any other problems, let me know!

maoueh commented 6 years ago

@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 :)

kferran commented 6 years ago

Still running into the same issue on my end after upgrading to version 4.4.2. http://prntscr.com/i2drtz

maoueh commented 6 years ago

@kferran Please open a new issue so we can track there. It might be related to windows. I have a Windows machine at home, if I have time, I will try to test it here. I'm wondering if my bin fix (#471) might be the culprit here.

benjtinsley commented 6 years ago

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\

benjtinsley commented 6 years ago

yes what @maoueh said. i think we can track this better in its own issue

kferran commented 6 years ago

I will open a new issue, but yeah I am running it from the app directory.

On Jan 18, 2018 2:36 PM, "Ben Tinsley" notifications@github.com wrote:

yes what @maoueh https://github.com/maoueh i think we can track this better in its own issue

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vigetlabs/blendid/issues/527#issuecomment-358789632, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC27Wa09qo9W-xTLhBcdA86OMPpCCvFks5tL7l6gaJpZM4RhcCc .

kferran commented 6 years ago

Moved the issue I am having to #532