Jaya Krishna Namburu

Effecting for using `styled-components` from [jspm](https://jspm.org/) too

@ellenchristine in your angular-cli the prefix and assets should refer to the paths as shown below. ``` "assets": [ "assets", "favicon.png" ], "prefix": "app" ``` Then refer it like this...

Place to look for, to make changes to enable the feature https://github.com/teleporthq/teleport-code-generators/blob/48be43d762946d091c2c2b21759658ad48d3c02e/packages/teleport-project-generator-next/src/utils.ts#L50

NextJS released a new update for the `Image` component. Probably we should look into that, it has better flexibility with styling. https://next-site-git-nextjs-12-2-blog.vercel.sh/docs/api-reference/next/future/image

May be we should keep an eye on this --> https://github.com/ionic-team/stencil/issues/1491

Hey @vladnicula the proposal looks really good, but I have a small doubts 1. Regarding the attribute``serve`` ~~~ "content": { "type": "image", "url" : "http://lorempixel.com/400/200/", "meta": { "serve": "local" }...

But this proposal makes the whole Schema much cleaner and more declarative on handling assets 😃 🎆

Yeah that clears a lot of doubts to me, so we will download the assets and make them available to the user when we are exporting the project right ?

But, downloading external dependencies are affected by the external situations which might affect the generators performance time right? 😅 ```Total time = Time taken for the code to generate +...

Makes a good fit, once the watcher is also added. Building all packages everytime for a change is still a little overkill. Everything is cached still 😓