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

angular-cli: Extensibility #2906

Closed
fkolar opened this issue Oct 26, 2016 · 20 comments
Closed

angular-cli: Extensibility #2906

fkolar opened this issue Oct 26, 2016 · 20 comments
Labels
feature Issue that requests a new feature type: faq

Comments

@fkolar
Copy link

fkolar commented Oct 26, 2016

This is more like feature and maybe this is already in the list.
Even all works great, I would like to extends angular-cli and have some hooks available, to I can plug in my custom-command that can be called everytime I spin a build, or anything while on ng serve I change something and the build refreshes.

ideally the command would be outside of node_modules/

Thanks,
-Fk

@grizzm0
Copy link
Contributor

grizzm0 commented Oct 26, 2016

You can create scripts in package.json that chains multiple commands together. And live-reload on ng serve is already a thing...

@fkolar
Copy link
Author

fkolar commented Oct 26, 2016

Right lets say I can use package.json from where I will execute a command, but does not help with live-reload - when running ng serve

@filipesilva
Copy link
Contributor

We plan to support addons in the future, yes. It's a post 1.0 concern at the moment.

@tuvokki
Copy link

tuvokki commented Mar 11, 2017

As I understand the cli is based on ember-cli, which supports the install action for installing addons:

Ember CLI will detect the presence of an addon by inspecting each of your applications dependencies and search their package.json files for the presence of ember-addon in the keywords section
See DEVELOPING ADDONS AND BLUEPRINTS

Is it possible to enable this?

@filipesilva
Copy link
Contributor

Just wanted to give an update: 1.0 is currently released, and we are looking at the design of an addon system for future major versions.

@fkolar
Copy link
Author

fkolar commented May 22, 2017

This is good news!! Is this going to be under wiki to look at ?

@fkolar
Copy link
Author

fkolar commented Aug 18, 2017

Are there any news on this ?

@filipesilva
Copy link
Contributor

We just added customizable blueprints (#7090, docs are still being created) so that bit is customizable, but there isn't any build step customization yet.

@fkolar
Copy link
Author

fkolar commented Aug 21, 2017

I see. I will just have to wait for this addons support that maybe allows me to extends or customize build steps. Any timeline for this?

But thanks for the prompt reply.

@filipesilva
Copy link
Contributor

No time to share yet, no. But will try to share it as soon as we can.

@ShadowManu
Copy link

I would like/recommend the team to be more open about the addon system. The feature has been postponed and delayed for several reason (you know them better) but let the community help you out! Trying to get it right just by yourselves will not produce as good results. Therefore, some recommendations:

  • An open process of whats the strategy in mind to allow extensibility, so people get an idea of what/how something can (or not) be done.

  • Open a space for discussion of it. Probably the community can provide some insights (particularly webpack-oriented folks) on how to make it better/simpler. If the addons ecosystem is for the community to populate, then hear what the community thinks/need and let us help you out on the design (implementation?) process.

  • Establish a public rough roadmap (with possible risks if needed). Some people exasperate (myself included in some stressful situations) when it hasn't been clear how much work/time is needed/used for the addon system. Since pre-1.0 release the standard response for extension issues has been "later". At least pinpointing which quarter of the year something is to be expected helps a lot.

I'm really enthusiastic to help on pug (jade) templating and service worker addons but I need you guys to be more open. Help me, help you, win-win :)

@Cito
Copy link

Cito commented Oct 20, 2017

An addon system has been promised as solution for extending the default webpack configuration. Currently, I cannot even do such a simple thing as adding a loader for *.graphql files without hacking node_modules/@angular/cli/models/webpack-configs/common.js.

If it will take too long to provide a proper addon system, it would be helpful to re-consider #1656 and at least provide an interim way of injecting webpack loaders using the angular-cli.json cofiguration. I really don't want to eject angular-cli just to be able to import *.graphql files.

@fkolar
Copy link
Author

fkolar commented Oct 20, 2017

Yeah. I am hacking too few files and next to it I have to have my own CLI script that initialize a few things ;-(

@chadbr
Copy link

chadbr commented Dec 5, 2017

@filipesilva

Any updates / branches I could look into?

I'm basically at a standstill on some authorization workflows I need to do...

I'm not sure if I should fork / maintain merges or... what.

Thanks - Chad

@hansl hansl added feature Issue that requests a new feature and removed type: enhancement labels Jan 30, 2018
@4F2E4A2E
Copy link

4F2E4A2E commented Feb 9, 2018

@hansl hansl unassigned filipesilva 3 days ago

I thought it's happening

@alfaproject
Copy link

Sucks not having an easy way to add a loader for .graphql files. ):

@jonahbron
Copy link

Having pre-build hooks would be really nice for compiling GRPC-Web stubs.

@hansl
Copy link
Contributor

hansl commented Aug 23, 2018

I'm going to close this as Architect and Schematics are covering those bases. Architect is going to be stable in 7.0.

@hansl hansl closed this as completed Aug 23, 2018
@chadbr
Copy link

chadbr commented Aug 23, 2018

@hansl great stuff by the way - congrats!

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Issue that requests a new feature type: faq
Projects
None yet
Development

No branches or pull requests