Feature Request: Don't use env, and clean up graceful-fs
I'm triyng to get ryuu up and running on cloud9.io, and I've run into a few issues.
The first one is that c9.io installs nvm by default, and the domo shell script doesn't like it:
woganmay:~ $ domo
/usr/bin/env: node --harmony: No such file or directory
I do have node, installed and managed via nvm:
woganmay:~ $ which node
/home/ubuntu/.nvm/versions/node/v6.1.0/bin/node
That's resolved through a symlink at /usr/bin/node - and in most cases a symlink like that should make node work correctly. Not for ryuu though, which is why I've had to change it from this:
#!/usr/bin/env node --harmony
To this:
#!/usr/bin/node --harmony
It now works more or less as expected.
woganmay:~ $ domo -v
(node:1635) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
2.16.0
And there's the second issue - the dependency for graceful-fs is outdated. I also get errors related to that when installing ryuu. Would be nice if they could be cleaned up
Comments
-
I still get this error when installing the latest version of ryuu:
npm WARN deprecated graceful-fs@3.0.8: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
0 -
Hello @woganmay, thanks for taking the time to post your question here. We are not currently supporting Cloud9 with our tool. This is a great idea though and I will make sure to get it on our backlog.
Our developer portal outlines the installation guidelines we currently support: https://developer.domo.com/docs/dev-studio/dev-studio-get-started
Would it be ok if I reach out sometime soon for some more information on how you are using Cloud9 as an online development environment?
Product Manager, Domo Apps0 -
Hi @product_John - I don't think it's as much about supporting cloud9 specifically, but more nvm generally, which is used pretty widely in the node community: https://github.com/creationix/nvm .
I'll be trying to set up Dev Studio on a pure Linux machine later today, and will test if nvm is really the cause.
And yes! Reach out whenever. You should be able to PM me directly here via Dojo.
0 -
I just tried setting it up on a brand new Linux Mint installation. I used the jessie/sid repository versions of Node, and ran into the same problem with the domo app - taking out "env" fixed it.
I'm going to rebuild the machine and try installing Node directly from their repositories.
0 -
@woganmay - let me go talk to our engineering group today. I mentioned this late last evening and their first reaction was that it should be fine. I might reach out for some more information from you if that is ok.
Product Manager, Domo Apps0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 296 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 614 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 729 Beast Mode
- 53 App Studio
- 40 Variables
- 677 Automate
- 173 Apps
- 451 APIs & Domo Developer
- 45 Workflows
- 8 DomoAI
- 34 Predict
- 14 Jupyter Workspaces
- 20 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 121 Manage
- 118 Governance & Security
- Domo Community Gallery
- 32 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive