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

Having nested node_modules and different build files #2

Open
ijpatricio opened this issue Mar 13, 2018 · 1 comment
Open

Having nested node_modules and different build files #2

ijpatricio opened this issue Mar 13, 2018 · 1 comment

Comments

@ijpatricio
Copy link

Hello @pi0

I've been playing around with this package, and i can relate to lot of needs.

I do something different, abut can leverage your package very well. Maybe you want to take a look?

Project: https://github.com/ijpatricio/laravel-mix-branches

Live demo: https://laravel-mix-branches.laravel.pt/

Project root has "root node_modules"

but then application areas may have different node_modules dependecies.

resources/assets/mix-branches has modules/packages folders. check inside.

App is TailwindCss, while Blog is not.
App is VueJs 2.5, Blog is Vue 1. (for whatever reason.. just for demo...)

What do you think?

@ijpatricio
Copy link
Author

Seems you have abandoned this package?

Have customized a little, and integrated with also modular backend. Check here...
https://github.com/ijpatricio/laravel-modules-multimix

Wanting a new feature, to control modules environment build (dev/prod), so that pre-commit hooks and stuf...

Will make a fork 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

1 participant