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

Asset building #4

Open
groenroos opened this issue Nov 3, 2020 · 1 comment
Open

Asset building #4

groenroos opened this issue Nov 3, 2020 · 1 comment
Assignees
Labels
feature Brand new features to Sapling

Comments

@groenroos
Copy link
Member

To truly live up to the philosophy of zero config development, Sapling should probably also include automatic asset building for JS & CSS preprocessors out of the box.

There's no point is writing some brand new API for this, so we can likely get away with just creating a light wrapper around Laravel Mix. Potentially generate the mix file automatically (where the user does not provide their own) based on the contents of a magical assets/ folder?

@groenroos groenroos self-assigned this Nov 3, 2020
@groenroos groenroos transferred this issue from saplingjs/sapling Nov 12, 2020
@groenroos
Copy link
Member Author

Moving this issue to the CLI, as this feels like something that probably shouldn't exist in the core by default, but is a good dependency to offer installation of in the CLI.

@groenroos groenroos added the feature Brand new features to Sapling label Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Brand new features to Sapling
Development

No branches or pull requests

1 participant