Closed sergeylukin closed 8 years ago
When trying again antwar --init project inside my ~/code directory I got this error: ...
Fixed. Try updating the CLI. The problem was that it tried to read antwar.config.js
even when initializing a project so I got rid of that in this particular case.
While that error was confusing, antwar did create an project folder with some files and so I proceeded with cd project and antwar --develop and got this output:
This might be harder to solve. npm changed peer dependency behavior in npm 3. And incidentally Antwar themes depend on that... Perhaps the most sensible solution would be to convert to regular dependencies? Any thoughts? What's the preferred way to deal with this in npm 3?
CC @eldh
@sergeylukin I replaced the peer dependencies with regular ones. Can you give it another go now?
Works like a charm!
Ok, great to hear!
Hi,
I'm eager to getting my hands dirty with antwar, however I faced some issues before I could even start working on a new project.
As described in Getting started guide I installed
antwar-cli
globally and after executingantwar --init project
I was getting error related toantwar
peerDependency. I've then executednpm i antwar -g
hoping to fix that and indeed didn't see that error again. However, that was still confusing. Did I do something wrong?When trying again
antwar --init project
inside my~/code
directory I got this error:While that error was confusing, antwar did create an
project
folder with some files and so I proceeded withcd project
andantwar --develop
and got this output:Please let me know what I'm doing wrong or what could be done to fix that.
Thank you, any help appreciated.
OS X
10.10.5
nodev4.1.1
npmv3.3.5