Deploy the API's giving no such file error

#1
weber@ubuntu:~/Documents/tachi-tms/tms-lite-api$ serverless deploy
Serverless: Bundling with Webpack...
Time: 727ms
Built at: 2019-03-16 17:03:18
        Asset      Size  Chunks             Chunk Names
    create.js  8.22 KiB       0  [emitted]  create
       get.js  8.11 KiB       1  [emitted]  get
    active.js  7.91 KiB       2  [emitted]  active
create.js.map  7.45 KiB       0  [emitted]  create
   get.js.map  7.02 KiB       1  [emitted]  get
active.js.map  6.89 KiB       2  [emitted]  active
Entrypoint create = create.js create.js.map
Entrypoint get = get.js get.js.map
Entrypoint active = active.js active.js.map
 [0] external "source-map-support/register" 42 bytes {0} {1} {2} [built]
 [1] external "babel-runtime/regenerator" 42 bytes {0} {1} {2} [built]
 [2] external "babel-runtime/helpers/asyncToGenerator" 42 bytes {0} {1} {2} [built]
 [3] ./libs/dynamodb-lib.js 741 bytes {0} {1} {2} [built]
 [4] external "aws-sdk" 42 bytes {0} {1} {2} [built]
 [5] ./libs/response-lib.js 762 bytes {0} {1} {2} [built]
 [6] external "babel-runtime/core-js/json/stringify" 42 bytes {0} {1} {2} [built]
 [7] ./create.js 2.39 KiB {0} [built]
 [8] external "uuid" 42 bytes {0} [built]
 [9] ./get.js 2.37 KiB {1} [built]
[10] ./active.js 2.15 KiB {2} [built]
Serverless: Package lock found - Using locked versions
Serverless: Packing external modules: source-map-support@^0.4.18, babel-runtime@^6.26.0, uuid@^3.3.2
Serverless: Packaging service...
Serverless: Uploading CloudFormation file to S3...
Serverless: Uploading artifacts...
 
  Error --------------------------------------------------
 
  ENOENT: no such file or directory, stat '/home/weber/Documents/tachi-tms/tms-lite-api/.serverless/.serverless/tms-lite-api.zip'
 
     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
 
  Your Environment Information -----------------------------
     OS:                     linux
     Node Version:           8.11.1
     Serverless Version:     1.39.0

Any ideas as to what could be causing this? The Zip files generates but I noticed the file path above is /.serverless/.serverless which seems wrong but I don’t know why it would be doing that.

0 Likes

#2

Here’s the bug report: Link

Rollback one version and you should be good to go:
npm i -g serverless@1.38.0

1 Like

#3

Thanks for helping out. Serverless broke their build…

0 Likes