Serverless Offline: Error while running handler, cannot find module












0















I've been trying to use serverless-offline / serverless-offline-python and a family of other node packages (serverless-s3-local for example) to build an offline testing environment for some lambdas that I've written.



Using serverless-offline-python, I am able to start my python lambdas and invoke each function manually with:



sls offline start --stage local --noTimeout --watch --port 3000
sls invoke local --stage local -f import-processor-stage-1 -d '{"event": "", "context": ""}'


This works, but doesn't quite simulate what the lambda is actually doing. Ideally, I would simulate an S3 bucket having a new object imported and that action would be the catalyst for the lambda (import-processor-stage-1).



Enter serverless-s3-local.



I've rigged up a pretty fantastic configuration with the plugin, but for some reason when serverless-s3-local goes to trigger an event to my lambda handler, I receive this error:



Error while running handler { Error: Cannot find module '/Users/user/Documents/project/manager/infra/main/import_processor_stage_1'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.createHandler (/usr/local/lib/node_modules/serverless-offline/src/functionHelper.js:167:17)
at Object.func (/Users/user/node_modules/serverless-s3-local/index.js:308:50)
at /Users/user/node_modules/serverless-s3-local/index.js:170:11
at SafeSubscriber.s3eventSubscription.client.s3Event.pipe.subscribe [as _next] (/Users/user/node_modules/serverless-s3-local/index.js:176:7)
at SafeSubscriber.__tryOrUnsub (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:270:10)
at SafeSubscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:212:14)
at Subscriber._next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:141:22)
at Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
at MergeMapSubscriber.notifyNext (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:159:22)
at InnerSubscriber._next (/Users/user/node_modules/rxjs/src/internal/InnerSubscriber.ts:17:17)
at InnerSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
at /Users/user/node_modules/rxjs/src/internal/util/subscribeToArray.ts:9:16
at Object.subscribeToResult (/Users/user/node_modules/rxjs/src/internal/util/subscribeToResult.ts:25:29)
at MergeMapSubscriber._innerSub (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:145:5)
at MergeMapSubscriber._tryNext (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:138:10)
at MergeMapSubscriber._next (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:122:12)
at MergeMapSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
at MapSubscriber._next (/Users/user/node_modules/rxjs/src/internal/operators/map.ts:86:22)
at MapSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
at Subject.next (/Users/user/node_modules/rxjs/src/internal/Subject.ts:68:17)
at triggerS3Event (/Users/user/node_modules/s3rver/lib/controllers.js:56:21)
at store.putObject (/Users/user/node_modules/s3rver/lib/controllers.js:498:11)
at storeMetadata.err (/Users/user/node_modules/s3rver/lib/stores/filesystem.js:291:13)
at /Users/user/node_modules/graceful-fs/graceful-fs.js:111:16
at /usr/local/lib/node_modules/serverless/node_modules/graceful-fs/graceful-fs.js:43:10
at FSReqWrap.oncomplete (fs.js:135:15) code: 'MODULE_NOT_FOUND' }


Sadly, I know that these plugins are in their enfancy (particularly serverless-offline-python), but I am quite sure that this should be a very easy fix. The module that is not found actually exists within the package! Im thinking that it is because it is a Python file and not a JS file. Is there a way within the js script to accept python files? So far, I have tried replacing all references of serverless-offline with serverless-offline-python within the serverless-s3-local code base, but I get the same error.



For reference, here is my serverless.yml file (for the record, the handler file is available, correctly located and works fine while manually invoking it):



service: catalog-import-manager

plugins:
- serverless-s3-local
- serverless-dynamodb-local
- serverless-offline-python

provider:
name: aws
runtime: python3.6
region: us-west-2


custom:
s3:
port: 8090
directory: s3-simulated-buckets
cors: false


resources:
Resources:
stage-one:
Type: 'AWS::DynamoDB::Table'
Properties:
AttributeDefinitions:
-
AttributeName: import_id
AttributeType: S
KeySchema:
-
AttributeName: import_id
KeyType: HASH
ProvisionedThroughput:
ReadCapacityUnits: 1
WriteCapacityUnits: 1
TableName: stage-one

ImportBucket:
Type: AWS::S3::Bucket
Properties:
BucketName: import


functions:
import-processor-stage-1:
handler: import_processor_stage_1.process_file_import
events:
- existingS3:
bucket: import
events:
- s3:ObjectCreated:*


Any and all help is appreciated! Thank you for taking a look!





Can confirm that this works for a js environment.










share|improve this question





























    0















    I've been trying to use serverless-offline / serverless-offline-python and a family of other node packages (serverless-s3-local for example) to build an offline testing environment for some lambdas that I've written.



    Using serverless-offline-python, I am able to start my python lambdas and invoke each function manually with:



    sls offline start --stage local --noTimeout --watch --port 3000
    sls invoke local --stage local -f import-processor-stage-1 -d '{"event": "", "context": ""}'


    This works, but doesn't quite simulate what the lambda is actually doing. Ideally, I would simulate an S3 bucket having a new object imported and that action would be the catalyst for the lambda (import-processor-stage-1).



    Enter serverless-s3-local.



    I've rigged up a pretty fantastic configuration with the plugin, but for some reason when serverless-s3-local goes to trigger an event to my lambda handler, I receive this error:



    Error while running handler { Error: Cannot find module '/Users/user/Documents/project/manager/infra/main/import_processor_stage_1'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.createHandler (/usr/local/lib/node_modules/serverless-offline/src/functionHelper.js:167:17)
    at Object.func (/Users/user/node_modules/serverless-s3-local/index.js:308:50)
    at /Users/user/node_modules/serverless-s3-local/index.js:170:11
    at SafeSubscriber.s3eventSubscription.client.s3Event.pipe.subscribe [as _next] (/Users/user/node_modules/serverless-s3-local/index.js:176:7)
    at SafeSubscriber.__tryOrUnsub (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:270:10)
    at SafeSubscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:212:14)
    at Subscriber._next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:141:22)
    at Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
    at MergeMapSubscriber.notifyNext (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:159:22)
    at InnerSubscriber._next (/Users/user/node_modules/rxjs/src/internal/InnerSubscriber.ts:17:17)
    at InnerSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
    at /Users/user/node_modules/rxjs/src/internal/util/subscribeToArray.ts:9:16
    at Object.subscribeToResult (/Users/user/node_modules/rxjs/src/internal/util/subscribeToResult.ts:25:29)
    at MergeMapSubscriber._innerSub (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:145:5)
    at MergeMapSubscriber._tryNext (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:138:10)
    at MergeMapSubscriber._next (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:122:12)
    at MergeMapSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
    at MapSubscriber._next (/Users/user/node_modules/rxjs/src/internal/operators/map.ts:86:22)
    at MapSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
    at Subject.next (/Users/user/node_modules/rxjs/src/internal/Subject.ts:68:17)
    at triggerS3Event (/Users/user/node_modules/s3rver/lib/controllers.js:56:21)
    at store.putObject (/Users/user/node_modules/s3rver/lib/controllers.js:498:11)
    at storeMetadata.err (/Users/user/node_modules/s3rver/lib/stores/filesystem.js:291:13)
    at /Users/user/node_modules/graceful-fs/graceful-fs.js:111:16
    at /usr/local/lib/node_modules/serverless/node_modules/graceful-fs/graceful-fs.js:43:10
    at FSReqWrap.oncomplete (fs.js:135:15) code: 'MODULE_NOT_FOUND' }


    Sadly, I know that these plugins are in their enfancy (particularly serverless-offline-python), but I am quite sure that this should be a very easy fix. The module that is not found actually exists within the package! Im thinking that it is because it is a Python file and not a JS file. Is there a way within the js script to accept python files? So far, I have tried replacing all references of serverless-offline with serverless-offline-python within the serverless-s3-local code base, but I get the same error.



    For reference, here is my serverless.yml file (for the record, the handler file is available, correctly located and works fine while manually invoking it):



    service: catalog-import-manager

    plugins:
    - serverless-s3-local
    - serverless-dynamodb-local
    - serverless-offline-python

    provider:
    name: aws
    runtime: python3.6
    region: us-west-2


    custom:
    s3:
    port: 8090
    directory: s3-simulated-buckets
    cors: false


    resources:
    Resources:
    stage-one:
    Type: 'AWS::DynamoDB::Table'
    Properties:
    AttributeDefinitions:
    -
    AttributeName: import_id
    AttributeType: S
    KeySchema:
    -
    AttributeName: import_id
    KeyType: HASH
    ProvisionedThroughput:
    ReadCapacityUnits: 1
    WriteCapacityUnits: 1
    TableName: stage-one

    ImportBucket:
    Type: AWS::S3::Bucket
    Properties:
    BucketName: import


    functions:
    import-processor-stage-1:
    handler: import_processor_stage_1.process_file_import
    events:
    - existingS3:
    bucket: import
    events:
    - s3:ObjectCreated:*


    Any and all help is appreciated! Thank you for taking a look!





    Can confirm that this works for a js environment.










    share|improve this question



























      0












      0








      0


      1






      I've been trying to use serverless-offline / serverless-offline-python and a family of other node packages (serverless-s3-local for example) to build an offline testing environment for some lambdas that I've written.



      Using serverless-offline-python, I am able to start my python lambdas and invoke each function manually with:



      sls offline start --stage local --noTimeout --watch --port 3000
      sls invoke local --stage local -f import-processor-stage-1 -d '{"event": "", "context": ""}'


      This works, but doesn't quite simulate what the lambda is actually doing. Ideally, I would simulate an S3 bucket having a new object imported and that action would be the catalyst for the lambda (import-processor-stage-1).



      Enter serverless-s3-local.



      I've rigged up a pretty fantastic configuration with the plugin, but for some reason when serverless-s3-local goes to trigger an event to my lambda handler, I receive this error:



      Error while running handler { Error: Cannot find module '/Users/user/Documents/project/manager/infra/main/import_processor_stage_1'
      at Function.Module._resolveFilename (module.js:547:15)
      at Function.Module._load (module.js:474:25)
      at Module.require (module.js:596:17)
      at require (internal/module.js:11:18)
      at Object.createHandler (/usr/local/lib/node_modules/serverless-offline/src/functionHelper.js:167:17)
      at Object.func (/Users/user/node_modules/serverless-s3-local/index.js:308:50)
      at /Users/user/node_modules/serverless-s3-local/index.js:170:11
      at SafeSubscriber.s3eventSubscription.client.s3Event.pipe.subscribe [as _next] (/Users/user/node_modules/serverless-s3-local/index.js:176:7)
      at SafeSubscriber.__tryOrUnsub (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:270:10)
      at SafeSubscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:212:14)
      at Subscriber._next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:141:22)
      at Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
      at MergeMapSubscriber.notifyNext (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:159:22)
      at InnerSubscriber._next (/Users/user/node_modules/rxjs/src/internal/InnerSubscriber.ts:17:17)
      at InnerSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
      at /Users/user/node_modules/rxjs/src/internal/util/subscribeToArray.ts:9:16
      at Object.subscribeToResult (/Users/user/node_modules/rxjs/src/internal/util/subscribeToResult.ts:25:29)
      at MergeMapSubscriber._innerSub (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:145:5)
      at MergeMapSubscriber._tryNext (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:138:10)
      at MergeMapSubscriber._next (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:122:12)
      at MergeMapSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
      at MapSubscriber._next (/Users/user/node_modules/rxjs/src/internal/operators/map.ts:86:22)
      at MapSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
      at Subject.next (/Users/user/node_modules/rxjs/src/internal/Subject.ts:68:17)
      at triggerS3Event (/Users/user/node_modules/s3rver/lib/controllers.js:56:21)
      at store.putObject (/Users/user/node_modules/s3rver/lib/controllers.js:498:11)
      at storeMetadata.err (/Users/user/node_modules/s3rver/lib/stores/filesystem.js:291:13)
      at /Users/user/node_modules/graceful-fs/graceful-fs.js:111:16
      at /usr/local/lib/node_modules/serverless/node_modules/graceful-fs/graceful-fs.js:43:10
      at FSReqWrap.oncomplete (fs.js:135:15) code: 'MODULE_NOT_FOUND' }


      Sadly, I know that these plugins are in their enfancy (particularly serverless-offline-python), but I am quite sure that this should be a very easy fix. The module that is not found actually exists within the package! Im thinking that it is because it is a Python file and not a JS file. Is there a way within the js script to accept python files? So far, I have tried replacing all references of serverless-offline with serverless-offline-python within the serverless-s3-local code base, but I get the same error.



      For reference, here is my serverless.yml file (for the record, the handler file is available, correctly located and works fine while manually invoking it):



      service: catalog-import-manager

      plugins:
      - serverless-s3-local
      - serverless-dynamodb-local
      - serverless-offline-python

      provider:
      name: aws
      runtime: python3.6
      region: us-west-2


      custom:
      s3:
      port: 8090
      directory: s3-simulated-buckets
      cors: false


      resources:
      Resources:
      stage-one:
      Type: 'AWS::DynamoDB::Table'
      Properties:
      AttributeDefinitions:
      -
      AttributeName: import_id
      AttributeType: S
      KeySchema:
      -
      AttributeName: import_id
      KeyType: HASH
      ProvisionedThroughput:
      ReadCapacityUnits: 1
      WriteCapacityUnits: 1
      TableName: stage-one

      ImportBucket:
      Type: AWS::S3::Bucket
      Properties:
      BucketName: import


      functions:
      import-processor-stage-1:
      handler: import_processor_stage_1.process_file_import
      events:
      - existingS3:
      bucket: import
      events:
      - s3:ObjectCreated:*


      Any and all help is appreciated! Thank you for taking a look!





      Can confirm that this works for a js environment.










      share|improve this question
















      I've been trying to use serverless-offline / serverless-offline-python and a family of other node packages (serverless-s3-local for example) to build an offline testing environment for some lambdas that I've written.



      Using serverless-offline-python, I am able to start my python lambdas and invoke each function manually with:



      sls offline start --stage local --noTimeout --watch --port 3000
      sls invoke local --stage local -f import-processor-stage-1 -d '{"event": "", "context": ""}'


      This works, but doesn't quite simulate what the lambda is actually doing. Ideally, I would simulate an S3 bucket having a new object imported and that action would be the catalyst for the lambda (import-processor-stage-1).



      Enter serverless-s3-local.



      I've rigged up a pretty fantastic configuration with the plugin, but for some reason when serverless-s3-local goes to trigger an event to my lambda handler, I receive this error:



      Error while running handler { Error: Cannot find module '/Users/user/Documents/project/manager/infra/main/import_processor_stage_1'
      at Function.Module._resolveFilename (module.js:547:15)
      at Function.Module._load (module.js:474:25)
      at Module.require (module.js:596:17)
      at require (internal/module.js:11:18)
      at Object.createHandler (/usr/local/lib/node_modules/serverless-offline/src/functionHelper.js:167:17)
      at Object.func (/Users/user/node_modules/serverless-s3-local/index.js:308:50)
      at /Users/user/node_modules/serverless-s3-local/index.js:170:11
      at SafeSubscriber.s3eventSubscription.client.s3Event.pipe.subscribe [as _next] (/Users/user/node_modules/serverless-s3-local/index.js:176:7)
      at SafeSubscriber.__tryOrUnsub (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:270:10)
      at SafeSubscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:212:14)
      at Subscriber._next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:141:22)
      at Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
      at MergeMapSubscriber.notifyNext (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:159:22)
      at InnerSubscriber._next (/Users/user/node_modules/rxjs/src/internal/InnerSubscriber.ts:17:17)
      at InnerSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
      at /Users/user/node_modules/rxjs/src/internal/util/subscribeToArray.ts:9:16
      at Object.subscribeToResult (/Users/user/node_modules/rxjs/src/internal/util/subscribeToResult.ts:25:29)
      at MergeMapSubscriber._innerSub (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:145:5)
      at MergeMapSubscriber._tryNext (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:138:10)
      at MergeMapSubscriber._next (/Users/user/node_modules/rxjs/src/internal/operators/mergeMap.ts:122:12)
      at MergeMapSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
      at MapSubscriber._next (/Users/user/node_modules/rxjs/src/internal/operators/map.ts:86:22)
      at MapSubscriber.Subscriber.next (/Users/user/node_modules/rxjs/src/internal/Subscriber.ts:101:12)
      at Subject.next (/Users/user/node_modules/rxjs/src/internal/Subject.ts:68:17)
      at triggerS3Event (/Users/user/node_modules/s3rver/lib/controllers.js:56:21)
      at store.putObject (/Users/user/node_modules/s3rver/lib/controllers.js:498:11)
      at storeMetadata.err (/Users/user/node_modules/s3rver/lib/stores/filesystem.js:291:13)
      at /Users/user/node_modules/graceful-fs/graceful-fs.js:111:16
      at /usr/local/lib/node_modules/serverless/node_modules/graceful-fs/graceful-fs.js:43:10
      at FSReqWrap.oncomplete (fs.js:135:15) code: 'MODULE_NOT_FOUND' }


      Sadly, I know that these plugins are in their enfancy (particularly serverless-offline-python), but I am quite sure that this should be a very easy fix. The module that is not found actually exists within the package! Im thinking that it is because it is a Python file and not a JS file. Is there a way within the js script to accept python files? So far, I have tried replacing all references of serverless-offline with serverless-offline-python within the serverless-s3-local code base, but I get the same error.



      For reference, here is my serverless.yml file (for the record, the handler file is available, correctly located and works fine while manually invoking it):



      service: catalog-import-manager

      plugins:
      - serverless-s3-local
      - serverless-dynamodb-local
      - serverless-offline-python

      provider:
      name: aws
      runtime: python3.6
      region: us-west-2


      custom:
      s3:
      port: 8090
      directory: s3-simulated-buckets
      cors: false


      resources:
      Resources:
      stage-one:
      Type: 'AWS::DynamoDB::Table'
      Properties:
      AttributeDefinitions:
      -
      AttributeName: import_id
      AttributeType: S
      KeySchema:
      -
      AttributeName: import_id
      KeyType: HASH
      ProvisionedThroughput:
      ReadCapacityUnits: 1
      WriteCapacityUnits: 1
      TableName: stage-one

      ImportBucket:
      Type: AWS::S3::Bucket
      Properties:
      BucketName: import


      functions:
      import-processor-stage-1:
      handler: import_processor_stage_1.process_file_import
      events:
      - existingS3:
      bucket: import
      events:
      - s3:ObjectCreated:*


      Any and all help is appreciated! Thank you for taking a look!





      Can confirm that this works for a js environment.







      python serverless-framework serverless-offline






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 21 '18 at 0:32







      Chad Van De Hey

















      asked Nov 20 '18 at 17:41









      Chad Van De HeyChad Van De Hey

      1,047816




      1,047816
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I ended up customizing the serverless-s3-local library to be able to call .py files. I may end up creating a new github repo and node package for this customization, but for now I will refer users to said customizations that I described here.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53398606%2fserverless-offline-error-while-running-handler-cannot-find-module%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I ended up customizing the serverless-s3-local library to be able to call .py files. I may end up creating a new github repo and node package for this customization, but for now I will refer users to said customizations that I described here.






            share|improve this answer




























              0














              I ended up customizing the serverless-s3-local library to be able to call .py files. I may end up creating a new github repo and node package for this customization, but for now I will refer users to said customizations that I described here.






              share|improve this answer


























                0












                0








                0







                I ended up customizing the serverless-s3-local library to be able to call .py files. I may end up creating a new github repo and node package for this customization, but for now I will refer users to said customizations that I described here.






                share|improve this answer













                I ended up customizing the serverless-s3-local library to be able to call .py files. I may end up creating a new github repo and node package for this customization, but for now I will refer users to said customizations that I described here.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 27 '18 at 22:51









                Chad Van De HeyChad Van De Hey

                1,047816




                1,047816






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53398606%2fserverless-offline-error-while-running-handler-cannot-find-module%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

                    SQL update select statement

                    'app-layout' is not a known element: how to share Component with different Modules