nativescript-cli: Dev Dependencies (like Gulp, etc) getting built and build is failing because of which Gulp integration is not working currently.

From @Headcult on April 26, 2016 11:30

Thanks for the amazing work on integrating Angular 2 with NativeScript at such a good pace. Looking forward for future releases.

The main issue that I’m facing now is: Dev Dependencies (like Gulp, etc) getting built and build is failing because of which Gulp integration is not working currently.

Can this be fixed at the earliest as we are unable to use Gulp within our project when using Angular 2 and NativeScript?

My Dev Dependencies:

"devDependencies": { "nativescript-dev-typescript": "^0.3.1", "shelljs": "^0.5.3", "typescript": "^1.8.9", "gulp": "^3.9.1", "gulp-debug": "^2.1.2", "gulp-typescript": "^2.12.1", "del": "^2.2.0", "run-sequence": "^1.1.4" }

Build Failure:

`:processDebugResources FAILED

FAILURE: Build failed with an exception.

  • What went wrong: Execution failed for task ‘:processDebugResources’.

    com.android.ide.common.process.ProcessException: org.gradle.process.internal.E xecException: Process ‘command ‘C:\Android\android-sdk\build-tools\23.0.3\aapt.e xe’’ finished with non-zero exit value 1`

Copied from original issue: NativeScript/nativescript-angular#195

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 23 (19 by maintainers)

Most upvoted comments

@Plamen5kov,

This method seems sketchy. Every time I add some NPM libraries I’m going to have to alter them from a package level? No one is going to want to do that.

Can’t we get the NativeScript CLI to remove certain files? Seems like it wouldn’t be too difficult to do.

Best,

Dragging our own pinned version of npm is a workaround that seems to work for many cases, but it’s nothing more than a workaround. I believe we have to get rid of it – the breakage caused by a command such as npm install (which is perfectly fine in any node project) is a real show stopper.

I’m probably oversimplifying everything, but can we rely on the user running npm install and use different module resolution strategies to identify modules we need to copy/update to <platform dir>/app/tns_modules?