question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

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

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:23 (19 by maintainers)

github_iconTop GitHub Comments

1reaction
nraboycommented, Jun 14, 2016

@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,

1reaction
hdeshevcommented, Jun 10, 2016

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?

Read more comments on GitHub >

github_iconTop Results From Across the Web

node.js - Gulp build is not working since devDependencies ...
I have an application in which I am trying to do npm install && then gulp build . It works fine unless I...
Read more >
Webpack or Browserify & Gulp: Which Is Better? - Toptal
Why Are Developers Using Webpack Instead of Gulp? Webpack is a bundler whereas Gulp is a task runner, so you'd expect to see...
Read more >
A complete toolchain for AngularJs - Gulp, Browserify, Sass
Have no dependencies to non-node tool chains; be exactly the same in both development and production; solve some Angular-specific issues: ...
Read more >
Everything that went wrong when deploying my Node + Hapi ...
The process for building all of the files to run this app goes like this: Compile the TypeScript files with the tsc command....
Read more >
rollup.js
rollup.config.js (building more than one bundle) export default [ { input: ... It is bad practice to mix default and named exports in...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found