Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot initialize Smoothie due to assets folder path issue #20

Open
kevinwo opened this issue Jan 22, 2018 · 3 comments
Open

Cannot initialize Smoothie due to assets folder path issue #20

kevinwo opened this issue Jan 22, 2018 · 3 comments

Comments

@kevinwo
Copy link

kevinwo commented Jan 22, 2018

Upon running mix smoothie.init, I receive the following error:

spawn: Could not cd to ./assets

I am using the latest commit, and my project assets are located at ./web/static/assets.

@stephenmoloney
Copy link
Collaborator

@kevinwo

Are you using a version of phoenix pre 1.3 ?

I think we must have lost compatibility for pre 1.3 versions by assuming assets are in ./assets

See here

I think it would be straight forward to make it cater for both directories...

@kevinwo
Copy link
Author

kevinwo commented Jan 22, 2018

Gotcha. I am using Phoenix 1.3, but now wondering if maybe I used a deprecated mix project initializer that created a pre 1.3 folder structure. Now that I'm comparing, it does look like my folder structure is pre 1.3.

I temporarily overrode the value for init.ex's @assets constant, and after getting the mix smoothie.init to work, realized I wanted to actually target my project root, where in pre 1.3 the node_modules folder and package.json file live.

@stephenmoloney
Copy link
Collaborator

yea... this is still an issue really though.. we should be supporting both paths... sure, leave this issue open for now...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants