https://serverless-stack.com/ logo
Join Slack
Powered by
hello everyone, this is my first day working using...
# help
s
hello everyone, this is my first day working using SST, when hitting the command 
npx sst start
the following problem occurs.
Copy code
Look like you're running sst for the first time in this directory. Please enter a stage name you'd like to use locally. Or hit enter to use the one based on your AWS credentials (samer): 
Using stage: samer
Preparing your SST app
Transpiling source
Linting source

=======================
 Deploying debug stack
=======================

Deploying stacks

 ❌  samer-notes-debug-stack failed: The samer-notes-debug-stack stack failed to deploy.


Stack samer-notes-debug-stack
  Status: failed
  Error: The samer-notes-debug-stack stack failed to deploy.
Cannot convert undefined or null to object
any thoughts?!
t
Woah that's strange
What version of SST are you on
s
@latest
here is the full debugging file
Copy code
0 info it worked if it ends with ok
1 verbose cli [ '/snap/node/5485/bin/node', '/snap/node/5485/bin/npm', 'start' ]
2 info using npm@6.14.15
3 info using node@v14.18.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle notes@0.1.0~prestart: notes@0.1.0
6 info lifecycle notes@0.1.0~start: notes@0.1.0
7 warn lifecycle The node binary used for scripts is /snap/bin/node but npm is using /snap/node/5485/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
8 verbose lifecycle notes@0.1.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle notes@0.1.0~start: PATH: /snap/node/5485/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/sam/Desktop/Work/UNI/Graduation/App/notes/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/home/sam/bin:/usr/lib/jvm/jdk-17/bin:/usr/lib/jvm/jdk-17/bin:/home/sam/bin:/usr/lib/jvm/jdk-17/bin:/usr/lib/jvm/jdk-17/bin:/home/sam/bin:/usr/lib/jvm/jdk-17/bin:/usr/lib/jvm/jdk-17/bin
10 verbose lifecycle notes@0.1.0~start: CWD: /home/sam/Desktop/Work/UNI/Graduation/App/notes
11 silly lifecycle notes@0.1.0~start: Args: [ '-c', 'sst start' ]
12 silly lifecycle notes@0.1.0~start: Returned: code: 1  signal: null
13 info lifecycle notes@0.1.0~start: Failed to exec start script
14 verbose stack Error: notes@0.1.0 start: `sst start`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/snap/node/5485/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
14 verbose stack     at EventEmitter.emit (events.js:400:28)
14 verbose stack     at ChildProcess.<anonymous> (/snap/node/5485/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
14 verbose stack     at ChildProcess.emit (events.js:400:28)
14 verbose stack     at maybeClose (internal/child_process.js:1058:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
15 verbose pkgid notes@0.1.0
16 verbose cwd /home/sam/Desktop/Work/UNI/Graduation/App/notes
17 verbose Linux 5.13.0-7620-generic
18 verbose argv "/snap/node/5485/bin/node" "/snap/node/5485/bin/npm" "start"
19 verbose node v14.18.1
20 verbose npm  v6.14.15
21 error code ELIFECYCLE
22 error errno 1
23 error notes@0.1.0 start: `sst start`
23 error Exit status 1
24 error Failed at the notes@0.1.0 start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
t
Can you show me the version from package.json
s
Copy code
{
  "name": "notes",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "test": "sst test",
    "start": "sst start",
    "build": "sst build",
    "deploy": "sst deploy",
    "remove": "sst remove"
  },
  "eslintConfig": {
    "extends": [
      "serverless-stack"
    ]
  },
  "devDependencies": {
    "@aws-cdk/assert": "1.126.0"
  },
  "dependencies": {
    "@serverless-stack/cli": "0.50.2",
    "@serverless-stack/resources": "0.50.2",
    "@aws-cdk/core": "1.126.0"
  }
}
solved! @thdxr 
The node binary used for scripts is /snap/bin/node but npm is using /snap/node/5485/bin/node itself. Use the
--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.`
thank you for your consideration
f
Hey @samer ewidat, is the debugging file you shared above from 
npm-debug.log
?
s
@Frank yes!
5 Views
Open in Slack
PreviousNext
Powered by