-
Notifications
You must be signed in to change notification settings - Fork 32
Unable to install StarterKit #11
Comments
The problem appears to be in the check for the existence of the Which part is considered the bug? The inclusion of the starterkit name in the path, or the check not taking the starterkit part of the path into account? |
I realize I'm following up on this really late but looks like I have a PR to fix this so I'll get that worked in so others can benefit from this. Sorry. |
I'm running this on Ubuntu 17.04 and I get this output with an error at the end
|
I was able to resolve this issue on a debian machine by installing the bsdtar package. |
@ shaal - I had the same problem on my windows-system. |
I encountered the same issue on a CI image running Alpine linux. Installing bsdtar fixed the issue for me as well. For Alpine, the command was: |
on Ubuntu 18, |
Yeah, unfortunately pattern-lab/patternlab-php-core#121 was closed without actually merging or fixing the dependency so working around it is sort of the only solution ATM. Feels kinda unmaintained. |
I ran into this issue too. In my case I'm running Docksal so I did this:
Then running npm start did not error out:
... based on this issue: My only issue remaining is that my Drupal emulsify theme (cloned to my own new theme) URL is wrong in terminal but sure enough, I can get to the Pattern Lab URL with |
Steps to reproduce:
composer create-project pattern-lab/edition-twig-standard [project-name]
1
and hit Enter.The wizard attempts to download the starter kit, but exists with the error:
the starterkit needs to contain a dist/ directory before it can be installed...
As we plan to build our own StarterKit, we do not require the base nor the demo to function properly, but I do need to understand how they should be structured as the demo, according to the Github source, appears to contain a dist/ directory, contrary to what the error message says.
The text was updated successfully, but these errors were encountered: