- Marcar como novo
- Marcador
- Subscrever
- Silenciar
- Subscrever fonte RSS
- Destacar
- Imprimir
- Denunciar conteúdo inapropriado
I was just wondering if there's a way to disable the fetching of bower components of my project. I have set a different installation directory in a .bowerrc file but it still installs in www/bower_components.
- Marcas:
- HTML5
- Intel® XDK
- Marcar como novo
- Marcador
- Subscrever
- Silenciar
- Subscrever fonte RSS
- Destacar
- Imprimir
- Denunciar conteúdo inapropriado
In the current release there is no way to override that directory location. At this time, these properties in your .bowerrc file are overridden by the implementation that is included in the XDK:
- proxy
- https-proxy
- analytics
- directory
- cwd
- interactive
The "directory" property will work in your .bowerrc file in a future release, but the others will likely continue to be overridden. Unfortunately, I am not allowed to publish an expected date for a release that will include that change.
Link copiado
- Marcar como novo
- Marcador
- Subscrever
- Silenciar
- Subscrever fonte RSS
- Destacar
- Imprimir
- Denunciar conteúdo inapropriado
In the current release there is no way to override that directory location. At this time, these properties in your .bowerrc file are overridden by the implementation that is included in the XDK:
- proxy
- https-proxy
- analytics
- directory
- cwd
- interactive
The "directory" property will work in your .bowerrc file in a future release, but the others will likely continue to be overridden. Unfortunately, I am not allowed to publish an expected date for a release that will include that change.
- Marcar como novo
- Marcador
- Subscrever
- Silenciar
- Subscrever fonte RSS
- Destacar
- Imprimir
- Denunciar conteúdo inapropriado
I'm not quite sure why you would force bower integration, but then ignore bower configurations. Seems like a very amateur decision.
Any idea of when we might be able to expect this bug fix would be helpful, because as is, XDK breaks all Ionic users by default.
- Marcar como novo
- Marcador
- Subscrever
- Silenciar
- Subscrever fonte RSS
- Destacar
- Imprimir
- Denunciar conteúdo inapropriado
I'm not quite sure why you would say that it seems like a very "amateur" decision.
I'm not forcing bower integration; Intel XDK just happens to have this new feature of managing your bower dependencies.
I'd like to ignore this specific configuration (installation directory of bower components) because it overrides my own. I've set it to a different directory so that the dependencies would not add up to the size of the built APKs/IPAs.
- Marcar como novo
- Marcador
- Subscrever
- Silenciar
- Subscrever fonte RSS
- Destacar
- Imprimir
- Denunciar conteúdo inapropriado
- Marcar como novo
- Marcador
- Subscrever
- Silenciar
- Subscrever fonte RSS
- Destacar
- Imprimir
- Denunciar conteúdo inapropriado
Guys, the reason we issue the EA version of the XDK is to get this sort of feedback up front, before it goes into the mainstream product. The Bower integration was in the EA release for several months before we released in the public release. Please checkout the EA releases so we can get this sort of feedback right away for other features we're working on. You can install both EA and the regular release on your machine at the same time, just cannot run them at the same time.

- Subscrever fonte RSS
- Marcar tópico como novo
- Marcar tópico como lido
- Flutuar este Tópico para o utilizador atual
- Marcador
- Subscrever
- Página amigável para impressora