Skip to content
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

[Bug]: No gulpfile found error when creating Dataverse TS Project #20

Closed
cfernandezcsp opened this issue Oct 27, 2021 · 4 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@cfernandezcsp
Copy link

Contact Details

cfernandez@creativityspark.es

What happened?

When clicking on the "Create Dataverse TS Project" context menu button on a folder, the terminal shows a "No gulpfile found" error.

Some project files are generated, but it seems like the process stops half way through.

The previous npm install command ends successfully.

I've tried installing gulp and adding a gulpfile.js on the project root folder, but it seems like what is missing is the gulp file in the typescript package.

Any ideas of what can be causing this?

P.S.: Excellent tool! Thanks for creating it!

What version of the tool are you using?

1.1.0

What version of Visual Studio Code are you running?

1.61.2

Relevant log output

PS C:\Users\xxx\Desktop\New folder> npm link typescript
npm ERR! code 1
npm ERR! path C:\Users\xxx\AppData\Roaming\npm\node_modules\typescript
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c gulp build-eslint-rules
npm ERR! [12:24:07] No gulpfile found

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\xxx\AppData\Local\npm-cache\_logs\2021-10-27T10_24_07_272Z-debug.log
@cfernandezcsp cfernandezcsp added the bug Something isn't working label Oct 27, 2021
@power-maverick-bot
Copy link

I am Groot!!
Thanks for opening your first issue here! Please make sure you have given us as much context as possible.
One of the Avengers will respond as soon as possible.

@Power-Maverick
Copy link
Owner

Ahh I think I know the issue. In the initial version I didnt had TypeScript in package.json and was assuming everyone will have it installed globally hence I needed link command to link it. In this release I removed that assumption and added it local to the project. So no need of that link command. I will update the tool but in meantime you can run npm install and you should be good.

Thanks for raising the issue. Will get the fix out pretty soon.

@Power-Maverick
Copy link
Owner

Fix is now available in 1.1.2 version. Also, improved the load time of the tool by 80% 🙌

@cfernandezcsp
Copy link
Author

Working great now! Thanks for the quick fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants