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

Frontools 2.0 #201

Closed
Igloczek opened this issue May 2, 2017 · 3 comments
Closed

Frontools 2.0 #201

Igloczek opened this issue May 2, 2017 · 3 comments

Comments

@Igloczek
Copy link
Contributor

Igloczek commented May 2, 2017

Idea:
Make Frontools a plugin system and publish only as Node.js package (npm) to improve extendability and modularity, making it more front-end oriented at same time.

Usage will be simple:
package.json

{
  "dependencies": {
    "magento2-frontools": "^2.0.0",
    "magento2-frontools-babel": "~0.2.0",
    "magento2-frontools-scss": "^1.0.0"
  }
}

Tools that might be useful:

@kjugi
Copy link
Contributor

kjugi commented Nov 15, 2017

Bring webpack here 😁

EDIT:
Or even this: https://github.com/parcel-bundler/parcel

@joshuaadickerson
Copy link

If you wanted to also support Composer installs (ugh), you could just check the parent directory name for config.projectPath. If it's composer, go up 3 directories. If it's node_modules, go up 2. You could even have it fallback to search for an app directory and inside that a design directory.

@Igloczek
Copy link
Contributor Author

@joshuaadickerson even if the core of Frontools will be available only as a Node.js package, there will be a Composer package required to deal with other required files like package.json and be able to use them in M2 project.

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

3 participants