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

add angular2 support #8

Open
venil7 opened this issue Jan 8, 2016 · 8 comments
Open

add angular2 support #8

venil7 opened this issue Jan 8, 2016 · 8 comments

Comments

@venil7
Copy link

venil7 commented Jan 8, 2016

No description provided.

@venil7
Copy link
Author

venil7 commented Jan 8, 2016

automatic compilation of TypeScript files?

@satya164
Copy link
Owner

satya164 commented Jan 8, 2016

@venil7 Doesn't Angular have it's own CLI?

@venil7
Copy link
Author

venil7 commented Jan 8, 2016

not AFAIK, it just seems like quik is very react centric, while it would be nice if it was library agnostic and be used with any es6 project. or maybe a plugin system, so that any transpiler, like TypeScript can be plugged in..

@satya164
Copy link
Owner

satya164 commented Jan 8, 2016

@venil7 I surely want to add other things. Will need to make the React bit rock solid, and have a plugin system to extend the webpack config. Wanna help?

@satya164
Copy link
Owner

satya164 commented Jan 8, 2016

BTW there are two ways to extend quik,

  1. Add custom loaders to the webpack config (there's no way to do this right now). This can be for simple things, like typescript support.
  2. Write middlewares to handle different file types. See the API docs. This can be for more sophisticated things, for example adding browserSync .

@venil7
Copy link
Author

venil7 commented Jan 9, 2016

yes, but i thought that the main idea was to have it zero-setup
so maybe if option 1 was included out of the box

@satya164
Copy link
Owner

satya164 commented Jan 9, 2016

@venil7 Yeah. But the reason I want to add a plugin system is so support for new things can be added easily. Fo example, right now, to add typescript support, you've to change files in 3 places, the webpack config, the middleware which handles JS and the middleware which handles hot reload. It'll be better to have those changes self-contained in one file.

Also, people will not need to fork it if they want a slightly different feature set. They can just add something on top of it and publish as a separate module.

BTW I spent some time yesterday night trying to add typescript. The problem I faced was that the ts-loder was trying to require modules from current directory and not quik's node_modules directory. Once I sort it out, I'll add typescript. Help is welcome.

@venil7
Copy link
Author

venil7 commented Jan 9, 2016

yeah, i agree on the plugin system,
as long as they are installable via npm

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

No branches or pull requests

2 participants