Is it Possible to integrate Uppy with ASP.net MVC application

Hi,
Thanks for the such a nice control.
I want to integrate this with my application create in ASP.Net MVC. I was able integreate basic functionlity of Uppy but facing difficulties to integrate Google Drive, Dropbox.
Could you please share steps to integreate in .NET MVC application. If possible please share example source code.
Many Thanks!!

Hi, the Google Drive and Dropbox integrations require use of Uppy Companion (previously Uppy Server), which is a separate Node.js application. Uppy Companion is required because third party integrations require authentication, which would be insecure if done from the browser alone. It should run as a separate application next to your ASP.NET application. There is some documentation on the website; because the rest of your application is not written in Node.js, the “standalone server” instructions are most relevant for you. Hope that helps you get started!

Is it possible to integrate Uppy Server into Web api instead of creating new standalone server.? are there any documentation for that?

How to configure Uppy Server on windows machine. I have followed the steps given on site but .sh file are not exuecuting on windows. Please help

You can only integrate it directly into an existing Node.js application, or run it as a standalone server but let ASP.NET proxy requests to it.

The .sh file in the documentation defines environment variables, which is done a bit differently on Windows… I don’t have a Windows machine at hand, but I think you need a batch file instead:

# any long set of random characters for the server session
set UPPYSERVER_SECRET="shh!Issa Secret!"
# corresponds to the server.host option
set UPPYSERVER_DOMAIN="YOUR SERVER DOMAIN"
# corresponds to the filePath option
set UPPYSERVER_DATADIR="PATH/TO/DOWNLOAD/DIRECTORY"

node ./path/to/companion/lib/standalone/start-server.js

Use set instead of export. That will define the environment variables and then run Uppy Companion, so Companion should inherit those variables.

Windows support has not been very high priority for us so apologies for it being a bit unclear!

Do you means that at this time I can’t run the Uppy Server on windows machine?

Even after adding SET instead of export , still it is not working

uppy-build@ start:companion D:\VSTS\uppyServer\uppy
sh ./bin/companion

‘sh’ is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! uppy-build@ start:companion: sh ./bin/companion
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the uppy-build@ start:companion script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\gjagdale\AppData\Roaming\npm-cache_logs\2018-08-20T17_49_22_313Z-debug.log

Please reply.
Thanks,

It probably works on windows, but I can’t guarantee it.

Run the batch file directly instead of doing npm start. Make sure to have the node ... line at the end of the file as in my example. If you save the batch file as start.cmd, do:

./start.cmd

As you said , I renamed file “\uppy\bin\companion” to “\uppy\bin\start.bat” , also added “node …” at the end of file but still received number of errors

env’ is not recognized as an internal or external command,
operable program or batch file.

D:\VSTS\uppyServer\uppy>UPPYSERVER_DATADIR="./output"
‘UPPYSERVER_DATADIR’ is not recognized as an internal or external command,
operable program or batch file.

D:\VSTS\uppyServer\uppy>UPPYSERVER_DOMAIN=“localhost:3020”
‘UPPYSERVER_DOMAIN’ is not recognized as an internal or external command,
operable program or batch file.

D:\VSTS\uppyServer\uppy>UPPYSERVER_PROTOCOL=“http”
‘UPPYSERVER_PROTOCOL’ is not recognized as an internal or external command,
operable program or batch file.

D:\VSTS\uppyServer\uppy>UPPYSERVER_PORT=3020
‘UPPYSERVER_PORT’ is not recognized as an internal or external command,
operable program or batch file.

D:\VSTS\uppyServer\uppy>UPPY_ENDPOINTS=""
‘UPPY_ENDPOINTS’ is not recognized as an internal or external command,
operable program or batch file.

D:\VSTS\uppyServer\uppy>UPPYSERVER_SECRET=“development”
‘UPPYSERVER_SECRET’ is not recognized as an internal or external command,
operable program or batch file.

D:\VSTS\uppyServer\uppy>nodemon --watch packages/@uppy/companion/src --exec node ./packages/@uppy/companion/src/standalone/start-server.js
‘nodemon’ is not recognized as an internal or external command,
operable program or batch file.

D:\VSTS\uppyServer\uppy>node …
module.js:538
throw err;
^

Error: Cannot find module ‘D:\VSTS\uppyServer\uppy…’
at Function.Module._resolveFilename (module.js:536:15)
at Function.Module._load (module.js:466:25)
at Function.Module.runMain (module.js:676:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3

Oh, I didn’t mean to rename the file, I meant creating a new one. This is more or less what you need:

The top screen is the full contents of start.cmd. The last line is just companion, because I installed it globally using npm install --global companion; you may have to specify the full path instead as in my first example (eg node ./path/to/companion/lib/standalone/start-server.js). The bottom screen is running that start.cmd file in PowerShell. It errors on the last line but that’s because the PATH/TO/DOWNLOAD/DIRECTORY doesn’t exist, it should be OK if you change it to a path that does exist :slight_smile:

Thanks for your reply…
I am able create cmd file and requred environment set.
Even i have set filePath , it is still giving me the error
Please specify the following options to run companion as Standalone:
“filePath”

Below is the start.cmd file

set UPPYSERVER_SECRET = “THisisSSs!!!Secret”
set UPPYSERVER_DOMAIN= “localhost”
SET UPPYSERVER_DATADIR = “D:\VSTS\uppyServer\uploddir”
SET filePath = “path/to/download/folder”
node “D:\VSTS\uppyServer\uppy\packages@uppy\companion\src\standalone\start-server.js”

Now I am able to configure Uppy standalone server… I have consume uppy on .net MVC application like below
var uppy = Uppy.Core({ autoProceed: false });

uppy.use(Uppy.Dashboard, { target: '#drag-drop-area', inline: true });
uppy.use(Uppy.XHRUpload, { endpoint: 'http://localhost:60461/Test/FileUpload' });
uppy.use(Uppy.GoogleDrive, { target: Uppy.Dashboard, serverUrl: 'http://localhost:3020' });
uppy.use(Uppy.Dropbox, { target: Uppy.Dashboard, serverUrl: 'http://localhost:3020/' });
uppy.use(Uppy.Instagram, { target: Uppy.Dashboard, serverUrl: 'http://localhost:3020/' });
uppy.use(Uppy.Webcam, { target: Uppy.Dashboard });

// uppy.use(Uppy.Tus, { endpoint: ‘https://master.tus.io/files/’ });

But the issue is , when I click on google drive , it shows nothing and I see the error in console
RequestClient.js:2 Uncaught (in promise) TypeError: Cannot read property ‘replace’ of undefined

Please help out here. … Thanks

Hmm, I recognise that message, but will need to dig a bit to find out what it was about. I’ll post here when I do. Are you using the latest version (v0.27.2)?

I am using CDN url in my ASP.Net application

and for companion I have install it using npm install so i think I am using latest version.

Thanks,

Any update on this?
please share.

Sorry, I’ve been traveling and not having a lot of Uppy time :slight_smile: I wasn’t able to dig up the replace issue. Can you confirm the versions you are using? Doing npm ls will show all installed packages and their versions.

When encountering an error, please share the full stack trace! It makes it easier to see what happened.

Stacktrace :

RequestClient.js:2 Uncaught (in promise) TypeError: Cannot read property ‘replace’ of undefined
at T (RequestClient.js:2)
at t.get (RequestClient.js:2)
at t.e._getUrl (RequestClient.js:2)
at t.e.get (RequestClient.js:2)
at t.checkAuth (RequestClient.js:4)
at e.checkAuth (Browser.js:3)
at t.componentDidMount (Loader.js:3)
at h (preact.js:2)
at f (preact.js:2)
at Object.render (preact.js:2)

Here is the version info

  • UNMET DEPENDENCY @uppy/fs-tail-stream@1.2.0
    | -- UNMET DEPENDENCY once@1.4.0 |– UNMET DEPENDENCY wrappy@1.0.2
    ±- UNMET DEPENDENCY atob@2.1.0
    ±- UNMET DEPENDENCY aws-sdk@2.291.0
    | ±- UNMET DEPENDENCY buffer@4.9.1
    | | ±- UNMET DEPENDENCY base64-js@1.3.0
    | | ±- UNMET DEPENDENCY ieee754@1.1.8
    | | -- UNMET DEPENDENCY isarray@1.0.0 | +-- UNMET DEPENDENCY events@1.1.1 | +-- UNMET DEPENDENCY ieee754@1.1.8 | +-- UNMET DEPENDENCY jmespath@0.15.0 | +-- UNMET DEPENDENCY querystring@0.2.0 | +-- UNMET DEPENDENCY sax@1.2.1 | +-- UNMET DEPENDENCY url@0.10.3 | | +-- UNMET DEPENDENCY punycode@1.3.2 | |– UNMET DEPENDENCY querystring@0.2.0
    | ±- UNMET DEPENDENCY uuid@3.1.0
    | -- UNMET DEPENDENCY xml2js@0.4.19 | +-- UNMET DEPENDENCY sax@1.2.1 |– UNMET DEPENDENCY xmlbuilder@9.0.7
    ±- UNMET DEPENDENCY body-parser@1.18.2
    | ±- UNMET DEPENDENCY bytes@3.0.0
    | ±- UNMET DEPENDENCY content-type@1.0.4
    | ±- UNMET DEPENDENCY debug@2.6.9
    | | -- UNMET DEPENDENCY ms@2.0.0 | +-- UNMET DEPENDENCY depd@1.1.2 | +-- UNMET DEPENDENCY http-errors@1.6.3 | | +-- UNMET DEPENDENCY depd@1.1.2 | | +-- UNMET DEPENDENCY inherits@2.0.3 | | +-- UNMET DEPENDENCY setprototypeof@1.1.0 | |– UNMET DEPENDENCY statuses@1.5.0
    | ±- UNMET DEPENDENCY iconv-lite@0.4.19
    | ±- UNMET DEPENDENCY on-finished@2.3.0
    | | -- UNMET DEPENDENCY ee-first@1.1.1 | +-- UNMET DEPENDENCY qs@6.5.1 | +-- UNMET DEPENDENCY raw-body@2.3.2 | | +-- UNMET DEPENDENCY bytes@3.0.0 | | +-- UNMET DEPENDENCY http-errors@1.6.2 | | | +-- UNMET DEPENDENCY depd@1.1.1 | | | +-- UNMET DEPENDENCY inherits@2.0.3 | | | +-- UNMET DEPENDENCY setprototypeof@1.0.3 | | |– UNMET DEPENDENCY statuses@1.5.0
    | | ±- UNMET DEPENDENCY iconv-lite@0.4.19
    | | -- UNMET DEPENDENCY unpipe@1.0.0 |– UNMET DEPENDENCY type-is@1.6.16
    | ±- UNMET DEPENDENCY media-typer@0.3.0
    | -- UNMET DEPENDENCY mime-types@2.1.19 +-- UNMET DEPENDENCY common-tags@1.8.0 +-- UNMET DEPENDENCY connect-redis@3.3.3 | +-- UNMET DEPENDENCY debug@3.1.0 | |– UNMET DEPENDENCY ms@2.0.0
    | -- UNMET DEPENDENCY redis@2.8.0 +-- UNMET DEPENDENCY cookie-parser@1.4.3 | +-- UNMET DEPENDENCY cookie@0.3.1 |– UNMET DEPENDENCY cookie-signature@1.0.6
    ±- UNMET DEPENDENCY express@4.16.3
    | ±- UNMET DEPENDENCY accepts@1.3.5
    | | ±- UNMET DEPENDENCY mime-types@2.1.19
    | | -- UNMET DEPENDENCY negotiator@0.6.1 | +-- UNMET DEPENDENCY array-flatten@1.1.1 | +-- UNMET DEPENDENCY body-parser@1.18.2 | +-- UNMET DEPENDENCY content-disposition@0.5.2 | +-- UNMET DEPENDENCY content-type@1.0.4 | +-- UNMET DEPENDENCY cookie@0.3.1 | +-- UNMET DEPENDENCY cookie-signature@1.0.6 | +-- UNMET DEPENDENCY debug@2.6.9 | +-- UNMET DEPENDENCY depd@1.1.2 | +-- UNMET DEPENDENCY encodeurl@1.0.2 | +-- UNMET DEPENDENCY escape-html@1.0.3 | +-- UNMET DEPENDENCY etag@1.8.1 | +-- UNMET DEPENDENCY finalhandler@1.1.1 | | +-- UNMET DEPENDENCY debug@2.6.9 | | +-- UNMET DEPENDENCY encodeurl@1.0.2 | | +-- UNMET DEPENDENCY escape-html@1.0.3 | | +-- UNMET DEPENDENCY on-finished@2.3.0 | | +-- UNMET DEPENDENCY parseurl@1.3.2 | | +-- UNMET DEPENDENCY statuses@1.4.0 | |– UNMET DEPENDENCY unpipe@1.0.0
    | ±- UNMET DEPENDENCY fresh@0.5.2
    | ±- UNMET DEPENDENCY merge-descriptors@1.0.1
    | ±- UNMET DEPENDENCY methods@1.1.2
    | ±- UNMET DEPENDENCY on-finished@2.3.0
    | ±- UNMET DEPENDENCY parseurl@1.3.2
    | ±- UNMET DEPENDENCY path-to-regexp@0.1.7
    | ±- UNMET DEPENDENCY proxy-addr@2.0.4
    | | ±- UNMET DEPENDENCY forwarded@0.1.2
    | | -- UNMET DEPENDENCY ipaddr.js@1.8.0 | +-- UNMET DEPENDENCY qs@6.5.1 | +-- UNMET DEPENDENCY range-parser@1.2.0 | +-- UNMET DEPENDENCY safe-buffer@5.1.1 | +-- UNMET DEPENDENCY send@0.16.2 | | +-- UNMET DEPENDENCY debug@2.6.9 | | +-- UNMET DEPENDENCY depd@1.1.2 | | +-- UNMET DEPENDENCY destroy@1.0.4 | | +-- UNMET DEPENDENCY encodeurl@1.0.2 | | +-- UNMET DEPENDENCY escape-html@1.0.3 | | +-- UNMET DEPENDENCY etag@1.8.1 | | +-- UNMET DEPENDENCY fresh@0.5.2 | | +-- UNMET DEPENDENCY http-errors@1.6.3 | | +-- UNMET DEPENDENCY mime@1.4.1 | | +-- UNMET DEPENDENCY ms@2.0.0 | | +-- UNMET DEPENDENCY on-finished@2.3.0 | | +-- UNMET DEPENDENCY range-parser@1.2.0 | |– UNMET DEPENDENCY statuses@1.4.0
    | ±- UNMET DEPENDENCY serve-static@1.13.2
    | | ±- UNMET DEPENDENCY encodeurl@1.0.2
    | | ±- UNMET DEPENDENCY escape-html@1.0.3
    | | ±- UNMET DEPENDENCY parseurl@1.3.2
    | | -- UNMET DEPENDENCY send@0.16.2 | +-- UNMET DEPENDENCY setprototypeof@1.1.0 | +-- UNMET DEPENDENCY statuses@1.4.0 | +-- UNMET DEPENDENCY type-is@1.6.16 | +-- UNMET DEPENDENCY utils-merge@1.0.1 |– UNMET DEPENDENCY vary@1.1.2
    ±- UNMET DEPENDENCY express-interceptor@1.2.0
    | -- UNMET DEPENDENCY debug@2.6.9 +-- UNMET DEPENDENCY express-prom-bundle@3.3.0 | +-- UNMET DEPENDENCY on-finished@2.3.0 | +-- UNMET DEPENDENCY prom-client@10.2.3 |– UNMET DEPENDENCY url-value-parser@1.0.0
    ±- UNMET DEPENDENCY express-session@1.15.6
    | ±- UNMET DEPENDENCY cookie@0.3.1
    | ±- UNMET DEPENDENCY cookie-signature@1.0.6
    | ±- UNMET DEPENDENCY crc@3.4.4
    | ±- UNMET DEPENDENCY debug@2.6.9
    | ±- UNMET DEPENDENCY depd@1.1.2
    | ±- UNMET DEPENDENCY on-headers@1.0.1
    | ±- UNMET DEPENDENCY parseurl@1.3.2
    | ±- UNMET DEPENDENCY uid-safe@2.1.5
    | | -- UNMET DEPENDENCY random-bytes@1.0.0 |– UNMET DEPENDENCY utils-merge@1.0.1
    ±- UNMET DEPENDENCY grant-express@4.1.2
    | -- UNMET DEPENDENCY grant@4.1.2 | +-- UNMET DEPENDENCY deep-copy@1.4.2 | +-- UNMET DEPENDENCY qs@6.5.1 | +-- UNMET DEPENDENCY request-compose@0.0.19 |– UNMET DEPENDENCY request-oauth@0.0.3
    | ±- UNMET DEPENDENCY oauth-sign@0.8.2
    | ±- UNMET DEPENDENCY qs@6.5.1
    | -- UNMET DEPENDENCY uuid@3.3.2 +-- UNMET DEPENDENCY helmet@3.8.2 | +-- UNMET DEPENDENCY connect@3.6.5 | | +-- UNMET DEPENDENCY debug@2.6.9 | | +-- UNMET DEPENDENCY finalhandler@1.0.6 | | | +-- UNMET DEPENDENCY debug@2.6.9 | | | +-- UNMET DEPENDENCY encodeurl@1.0.2 | | | +-- UNMET DEPENDENCY escape-html@1.0.3 | | | +-- UNMET DEPENDENCY on-finished@2.3.0 | | | +-- UNMET DEPENDENCY parseurl@1.3.2 | | | +-- UNMET DEPENDENCY statuses@1.3.1 | | |– UNMET DEPENDENCY unpipe@1.0.0
    | | ±- UNMET DEPENDENCY parseurl@1.3.2
    | | -- UNMET DEPENDENCY utils-merge@1.0.1 | +-- UNMET DEPENDENCY dns-prefetch-control@0.1.0 | +-- UNMET DEPENDENCY dont-sniff-mimetype@1.0.0 | +-- UNMET DEPENDENCY expect-ct@0.1.0 | +-- UNMET DEPENDENCY frameguard@3.0.0 | +-- UNMET DEPENDENCY helmet-csp@2.5.1 | | +-- UNMET DEPENDENCY camelize@1.0.0 | | +-- UNMET DEPENDENCY content-security-policy-builder@1.1.0 | | |– UNMET DEPENDENCY dashify@0.2.2
    | | ±- UNMET DEPENDENCY dasherize@2.0.0
    | | ±- UNMET DEPENDENCY lodash.reduce@4.6.0
    | | -- UNMET DEPENDENCY platform@1.3.4 | +-- UNMET DEPENDENCY hide-powered-by@1.0.0 | +-- UNMET DEPENDENCY hpkp@2.0.0 | +-- UNMET DEPENDENCY hsts@2.1.0 | +-- UNMET DEPENDENCY ienoopen@1.0.0 | +-- UNMET DEPENDENCY nocache@2.0.0 | +-- UNMET DEPENDENCY referrer-policy@1.1.0 |– UNMET DEPENDENCY x-xss-protection@1.0.0
    ±- UNMET DEPENDENCY isobject@3.0.1
    ±- UNMET DEPENDENCY jsonwebtoken@8.3.0
    | ±- UNMET DEPENDENCY jws@3.1.5
    | | ±- UNMET DEPENDENCY jwa@1.1.6
    | | | ±- UNMET DEPENDENCY buffer-equal-constant-time@1.0.1
    | | | ±- UNMET DEPENDENCY ecdsa-sig-formatter@1.0.10
    | | | | -- UNMET DEPENDENCY safe-buffer@5.1.1 | | |– UNMET DEPENDENCY safe-buffer@5.1.1
    | | -- UNMET DEPENDENCY safe-buffer@5.1.1 | +-- UNMET DEPENDENCY lodash.includes@4.3.0 | +-- UNMET DEPENDENCY lodash.isboolean@3.0.3 | +-- UNMET DEPENDENCY lodash.isinteger@4.0.4 | +-- UNMET DEPENDENCY lodash.isnumber@3.0.3 | +-- UNMET DEPENDENCY lodash.isplainobject@4.0.6 | +-- UNMET DEPENDENCY lodash.isstring@4.0.1 | +-- UNMET DEPENDENCY lodash.once@4.1.1 |– UNMET DEPENDENCY ms@2.1.1
    ±- UNMET DEPENDENCY lodash.merge@4.6.1
    ±- UNMET DEPENDENCY morgan@1.9.0
    | ±- UNMET DEPENDENCY basic-auth@2.0.0
    | | -- UNMET DEPENDENCY safe-buffer@5.1.1 | +-- UNMET DEPENDENCY debug@2.6.9 | +-- UNMET DEPENDENCY depd@1.1.2 | +-- UNMET DEPENDENCY on-finished@2.3.0 |– UNMET DEPENDENCY on-headers@1.0.1
    ±- UNMET DEPENDENCY ms@2.1.1
    ±- UNMET DEPENDENCY node-redis-pubsub@2.0.0
    | -- UNMET DEPENDENCY redis@2.8.0 +-- UNMET DEPENDENCY node-schedule@1.3.0 | +-- UNMET DEPENDENCY cron-parser@2.5.0 | | +-- UNMET DEPENDENCY is-nan@1.2.1 | | |– UNMET DEPENDENCY define-properties@1.1.2
    | | | ±- UNMET DEPENDENCY foreach@2.0.5
    | | | -- UNMET DEPENDENCY object-keys@1.0.12 | |– UNMET DEPENDENCY moment-timezone@0.5.21
    | | -- UNMET DEPENDENCY moment@2.22.2 | +-- UNMET DEPENDENCY long-timeout@0.1.1 |– UNMET DEPENDENCY sorted-array-functions@1.2.0
    ±- UNMET DEPENDENCY prom-client@10.2.3
    | -- UNMET DEPENDENCY tdigest@0.1.1 |– UNMET DEPENDENCY bintrees@1.0.1
    ±- UNMET DEPENDENCY purest@3.0.0
    | ±- UNMET DEPENDENCY @purest/config@1.0.1
    | | -- UNMET DEPENDENCY extend@3.0.2 | +-- UNMET DEPENDENCY @request/api@0.6.0 | | +-- UNMET DEPENDENCY @request/interface@0.1.0 | | +-- UNMET DEPENDENCY deep-copy@1.4.2 | |– UNMET DEPENDENCY extend@3.0.2
    | -- UNMET DEPENDENCY extend@3.0.2 +-- UNMET DEPENDENCY redis@2.8.0 | +-- UNMET DEPENDENCY double-ended-queue@2.1.0-0 | +-- UNMET DEPENDENCY redis-commands@1.3.5 |– UNMET DEPENDENCY redis-parser@2.6.0
    ±- UNMET DEPENDENCY request@2.85.0
    | ±- UNMET DEPENDENCY aws-sign2@0.7.0
    | ±- UNMET DEPENDENCY aws4@1.8.0
    | ±- UNMET DEPENDENCY caseless@0.12.0
    | ±- UNMET DEPENDENCY combined-stream@1.0.6
    | | -- UNMET DEPENDENCY delayed-stream@1.0.0 | +-- UNMET DEPENDENCY extend@3.0.2 | +-- UNMET DEPENDENCY forever-agent@0.6.1 | +-- UNMET DEPENDENCY form-data@2.3.2 | | +-- UNMET DEPENDENCY asynckit@0.4.0 | | +-- UNMET DEPENDENCY combined-stream@1.0.6 | |– UNMET DEPENDENCY mime-types@2.1.19
    | ±- UNMET DEPENDENCY har-validator@5.0.3
    | | ±- UNMET DEPENDENCY ajv@5.5.2
    | | | ±- UNMET DEPENDENCY co@4.6.0
    | | | ±- UNMET DEPENDENCY fast-deep-equal@1.1.0
    | | | ±- UNMET DEPENDENCY fast-json-stable-stringify@2.0.0
    | | | -- UNMET DEPENDENCY json-schema-traverse@0.3.1 | |– UNMET DEPENDENCY har-schema@2.0.0
    | ±- UNMET DEPENDENCY hawk@6.0.2
    | | ±- UNMET DEPENDENCY boom@4.3.1
    | | | -- UNMET DEPENDENCY hoek@4.2.1 | | +-- UNMET DEPENDENCY cryptiles@3.1.2 | | |– UNMET DEPENDENCY boom@5.2.0
    | | | -- UNMET DEPENDENCY hoek@4.2.1 | | +-- UNMET DEPENDENCY hoek@4.2.1 | |– UNMET DEPENDENCY sntp@2.1.0
    | | -- UNMET DEPENDENCY hoek@4.2.1 | +-- UNMET DEPENDENCY http-signature@1.2.0 | | +-- UNMET DEPENDENCY assert-plus@1.0.0 | | +-- UNMET DEPENDENCY jsprim@1.4.1 | | | +-- UNMET DEPENDENCY assert-plus@1.0.0 | | | +-- UNMET DEPENDENCY extsprintf@1.3.0 | | | +-- UNMET DEPENDENCY json-schema@0.2.3 | | |– UNMET DEPENDENCY verror@1.10.0
    | | | ±- UNMET DEPENDENCY assert-plus@1.0.0
    | | | ±- UNMET DEPENDENCY core-util-is@1.0.2
    | | | -- UNMET DEPENDENCY extsprintf@1.3.0 | |– UNMET DEPENDENCY sshpk@1.14.2
    | | ±- UNMET DEPENDENCY asn1@0.2.4
    | | | -- UNMET DEPENDENCY safer-buffer@2.1.2 | | +-- UNMET DEPENDENCY assert-plus@1.0.0 | | +-- UNMET OPTIONAL DEPENDENCY bcrypt-pbkdf@1.0.2 | | |– UNMET OPTIONAL DEPENDENCY tweetnacl@0.14.5
    | | ±- UNMET DEPENDENCY dashdash@1.14.1
    | | | -- UNMET DEPENDENCY assert-plus@1.0.0 | | +-- UNMET OPTIONAL DEPENDENCY ecc-jsbn@0.1.2 | | | +-- UNMET OPTIONAL DEPENDENCY jsbn@0.1.1 | | |– UNMET DEPENDENCY safer-buffer@2.1.2
    | | ±- UNMET DEPENDENCY getpass@0.1.7
    | | | -- UNMET DEPENDENCY assert-plus@1.0.0 | | +-- UNMET OPTIONAL DEPENDENCY jsbn@0.1.1 | | +-- UNMET DEPENDENCY safer-buffer@2.1.2 | |– UNMET OPTIONAL DEPENDENCY tweetnacl@0.14.5
    | ±- UNMET DEPENDENCY is-typedarray@1.0.0
    | ±- UNMET DEPENDENCY isstream@0.1.2
    | ±- UNMET DEPENDENCY json-stringify-safe@5.0.1
    | ±- UNMET DEPENDENCY mime-types@2.1.19
    | | -- UNMET DEPENDENCY mime-db@1.35.0 | +-- UNMET DEPENDENCY oauth-sign@0.8.2 | +-- UNMET DEPENDENCY performance-now@2.1.0 | +-- UNMET DEPENDENCY qs@6.5.1 | +-- UNMET DEPENDENCY safe-buffer@5.1.1 | +-- UNMET DEPENDENCY stringstream@0.0.6 | +-- UNMET DEPENDENCY tough-cookie@2.3.4 | |– UNMET DEPENDENCY punycode@1.4.1
    | ±- UNMET DEPENDENCY tunnel-agent@0.6.0
    | | -- UNMET DEPENDENCY safe-buffer@5.1.1 |– UNMET DEPENDENCY uuid@3.3.2
    ±- UNMET DEPENDENCY serialize-error@2.1.0
    ±- UNMET DEPENDENCY tus-js-client@1.5.1
    | ±- UNMET DEPENDENCY buffer-from@0.1.2
    | ±- UNMET DEPENDENCY extend@3.0.2
    | ±- UNMET DEPENDENCY lodash.throttle@4.1.1
    | -- UNMET DEPENDENCY resolve-url@0.2.1 +-- UNMET DEPENDENCY uuid@2.0.2 +-- UNMET DEPENDENCY validator@9.4.1– UNMET DEPENDENCY ws@1.1.5
    ±- UNMET DEPENDENCY options@0.0.6
    `-- UNMET DEPENDENCY ultron@1.0.2

I’m sorry, I’m not really sure what’s wrong there :frowning:

Please make sure you’re using the latest Uppy client version (0.27.5):

<script src="https://transloadit.edgly.net/releases/uppy/v0.27.5/dist/uppy.min.js"></script>

Please help i’m also getting the same error. Not able to run companion standalone server
Like this
C:\Users\nithi\Documents\uppy\packages@uppy\companion\src\standalone>node start-server.js
uppy: 2019-01-18T06:45:16.044Z [warn] startup.secret auto-generating server secret because none was specified
Please specify the following options to run companion as Standalone:
“filePath”,
“server.host”

I am also not able to run as standalone server and also not able to integrate with Asp.Net MVC Applicaiton

Please update here if you get any solution. I’m also integrating this in Angularjs application.

Hi @Ganesh,
How are you?
did you solved your issue to integrate with .net application?
I also looking for solution with uppy with google drive…