-
-
Notifications
You must be signed in to change notification settings - Fork 241
shell:depNSInit - Task "default" not found. #9
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
Comments
@NathanWalker, this is weird. It looks like the grunt task runner hasn't found its gruntfile.js or is running in a different folder, but I can't tell for sure. Can you tell me if your submodules have been updated correctly and the deps/NativeScript folder contains the {N} modules' code? Also, what OS are you running? I just tested this on Windows and Linux and while I got bitten by other problems (like updated definitions brought by the tsd tool that need some tweaking to work), I did not get the error you pasted above. |
Hit the "Comment" button too soon. I fixed the I'll merge it to master in a day or two. |
That branch seems to fix it 👍 thanks! |
Nvm :( I get this when I
|
Those RenderViewWithFragments shouldn't be there -- the deps/angular submodule shouldn't be updated to the latest fragments-based code (I'm working on supporting that one right now). You could either wait 1-2 days until I get it running and pushed to master, or check if the modules below deps point to the correct SHA's. Did you by any chance clone and get the latest angular codebase in there? |
I'll wait til' you get it merged to master, no worries. Thank @hdeshev ! Not sure what the deal is with the submodules. I've honestly never been a big fan of git submodules, always something funky. Seems using node and package.json (or bower) to manage all that works better. |
We'll be switching to the angular alpha builds on npm soon. I'm really looking forward to getting rid of submodules too. :-) |
Great to hear. I'd love to contribute to this project once I can at least run it for the first time 👍 |
This is no longer an issue for me. The usage of webpack is a welcome addition, nice! |
When getting the project setup and you get to the
grunt prepare
step, it runs a series of tasks where this happens...Running "shell:depNSInit" (shell) task
SOLINK_MODULE(target) Release/.node
CXX(target) Release/obj.target/fse/fsevents.o
SOLINK_MODULE(target) Release/fse.node
[email protected] ../../node_modules/grunt-ts
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected], [email protected], [email protected])
├── [email protected]
└── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
src/
Warning: Task "default" not found. Use --force to continue.
Aborted due to warnings.
Warning: Command failed: /bin/sh -c npm install&&grunt --no-runtslint
Use --force to continue.
Aborted due to warnings.
The text was updated successfully, but these errors were encountered: