The apollo-typed-lambda from tomyitav

changing port 3000

Hi, congrats on the great project; I'm trying to run it locally, but need to change the default port from 3000 to something else; can you please improve the readme to specify which config file should be changed to use a port other than 3000?

Getting issues while running on Windows 10

I cloned and tried to run this code

"npm run build"

and getting following error. Same time it works fine on Mac and Ubuntu

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'build' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle @tomyitav/[email protected]~prebuild: @tomyitav/[email protected]
6 verbose lifecycle @tomyitav/[email protected]~prebuild: unsafe-perm in lifecycle true
7 verbose lifecycle @tomyitav/[email protected]~prebuild: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;F:\zzz\apollo-typed-lambda\node_modules\.bin;C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Docker\Docker\Resources\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\nodejs\;C:\Program Files (x86)\Bitvise SSH Client;C:\Program Files\Git\cmd;C:\Users\Huang-PC\AppData\Local\Microsoft\WindowsApps;C:\Users\Huang-PC\AppData\Roaming\npm;C:\Users\Huang-PC\AppData\Local\Programs\Microsoft VS Code\bin
8 verbose lifecycle @tomyitav/[email protected]~prebuild: CWD: F:\zzz\apollo-typed-lambda
9 silly lifecycle @tomyitav/[email protected]~prebuild: Args: [ '/d /s /c', 'npm run clean && npm run generate' ]
10 silly lifecycle @tomyitav/[email protected]~prebuild: Returned: code: 1  signal: null
11 info lifecycle @tomyitav/[email protected]~prebuild: Failed to exec prebuild script
12 verbose stack Error: @tomyitav/[email protected] prebuild: `npm run clean && npm run generate`
12 verbose stack Exit status 1
12 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
12 verbose stack     at EventEmitter.emit (events.js:198:13)
12 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
12 verbose stack     at ChildProcess.emit (events.js:198:13)
12 verbose stack     at maybeClose (internal/child_process.js:982:16)
12 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
13 verbose pkgid @tomyitav/[email protected]
14 verbose cwd F:\zzz\apollo-typed-lambda
15 verbose Windows_NT 10.0.14393
16 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
17 verbose node v10.16.3
18 verbose npm  v6.9.0
19 error code ELIFECYCLE
20 error errno 1
21 error @tomyitav/[email protected] prebuild: `npm run clean && npm run generate`
21 error Exit status 1
22 error Failed at the @tomyitav/[email protected] prebuild script.
22 error This is probably not a problem with npm. There is likely additional logging output above.
23 verbose exit [ 1, true ]

Dependency deprecation warning: tsc (npm)

On registry https://registry.npmjs.org/, the "latest" version (v1.20150623.0) of dependency tsc has the following deprecation notice:

You probably meant to instally 'typescript'. Run 'npm install typescript -g'

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about tsc's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

Cold start time and package size too high

Problem

Lambda cold start with this setup takes around 1ms which seems to be a bit too high, considering that if used with RDS and an ORM it would probably go even higher. Also, the package size is around 6MB which is sub-optimal.

I'd love to see these issues addressed or at least some help with how to get on track towards solving them.

What I tried

serverless-plugin-optimize and serverless-plugin-webpack

This has resulted in the following error:

{
    "errorType": "Error",
    "errorMessage": "Unable to find package.json in any of:\n[/var/task/_optimize/serverless-graphql-dev-graphql,\n/var/task]",
    "stack": [
        "Error: Unable to find package.json in any of:",
        "[/var/task/_optimize/serverless-graphql-dev-graphql,",
        "/var/task]",
        "    at init (/var/task/_optimize/serverless-graphql-dev-graphql/lambda.js:61126:35)",
        "    at Object.463.. (/var/task/_optimize/serverless-graphql-dev-graphql/lambda.js:61161:29)",
        "    at o (/var/task/_optimize/serverless-graphql-dev-graphql/lambda.js:43:17)",
        "    at /var/task/_optimize/serverless-graphql-dev-graphql/lambda.js:43:75",
        "    at Object.1../core/injector (/var/task/_optimize/serverless-graphql-dev-graphql/lambda.js:47:17)",
        "    at o (/var/task/_optimize/serverless-graphql-dev-graphql/lambda.js:43:17)",
        "    at /var/task/_optimize/serverless-graphql-dev-graphql/lambda.js:43:75",
        "    at Object.12../dist/aws-wrapper (/var/task/_optimize/serverless-graphql-dev-graphql/lambda.js:174:38)",
        "    at o (/var/task/_optimize/serverless-graphql-dev-graphql/lambda.js:43:17)",
        "    at r (/var/task/_optimize/serverless-graphql-dev-graphql/lambda.js:45:9)"
    ]

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Warning

These dependencies are deprecated:

Datasource	Name	Replacement PR?
npm	`@types/graphql`
npm	`merge-graphql-schemas`
npm	`tslint`
npm	`tslint-react`

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Update dependency @types/node to v12.20.55
Update dependency core-js to v3.37.1
Update dependency graphql to v14.7.0 (graphql, @types/graphql)
Update dependency zone.js to v0.14.7
Click on this checkbox to rebase all open PRs at once

Detected dependencies

npm

package.json

apollo-server-lambda 2.6.4

core-js 3.1.4

graphql 14.3.1

graphql-tools 4.0.4

injection-js 2.2.1

merge-graphql-schemas 1.5.8

module-alias 2.2.2

reflect-metadata 0.1.13

zone.js 0.9.1

@graphql-codegen/cli 1.2.1

@graphql-codegen/typescript 1.2.1

@graphql-codegen/typescript-operations 1.2.1

@types/graphql 14.2.1

@types/node 12.0.12

husky 2.4.1

lint-staged 8.2.1

prettier 1.18.2

rimraf 2.6.3

serverless-dotenv-plugin 2.1.1

serverless-offline 5.3.3

tslint 5.18.0

tslint-config-prettier 1.18.0

tslint-eslint-rules 5.4.0

tslint-react 4.0.0

typescript 3.5.3

Check this box to trigger a request for Renovate to run again on this repository

tomyitav / apollo-typed-lambda Goto Github PK

apollo-typed-lambda's People

Contributors

Stargazers

Watchers

Forkers

apollo-typed-lambda's Issues

changing port 3000

Getting issues while running on Windows 10

Dependency deprecation warning: tsc (npm)

Cold start time and package size too high

Problem

What I tried

Dependency Dashboard

Rate-Limited

Edited/Blocked

Open

Detected dependencies

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent