```markroden@mmr-laptop:~/src/evidence/evidence-ba...
# troubleshooting
r
Copy code
markroden@mmr-laptop:~/src/evidence/evidence-based-reporting$ npm version
{
  'my-evidence-project': '0.0.1',
  npm: '8.5.1',
  node: '12.22.9',
  v8: '7.8.279.23-node.56',
  uv: '1.43.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.18.1',
  modules: '72',
  nghttp2: '1.43.0',
  napi: '8',
  llhttp: '2.1.4',
  http_parser: '2.9.4',
  openssl: '1.1.1m',
  cldr: '40.0',
  icu: '70.1',
  tz: '2022g',
  unicode: '14.0'
}
markroden@mmr-laptop:~/src/evidence/evidence-based-reporting$ npm run dev

> my-evidence-project@0.0.1 dev
> evidence dev -o

file:///home/markroden/src/evidence/evidence-based-reporting/node_modules/@sveltejs/kit/dist/cli.js:861
			https = https || !!vite_config.server?.https;
			                                      ^

SyntaxError: Unexpected token '.'
    at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)
markroden@mmr-laptop:~/src/evidence/evidence-based-reporting$
b
Your node version is too old I think
try installing node > v16
r
ok
I've also tried using docker, figuring it was something like that
I got this:
Copy code
markroden@mmr-laptop:~/src/evidence/evidence-based-reporting$ sudo ../docker-devenv/start-devenv.sh 
Starting Evidence with project root set to /home/markroden/src/evidence/evidence-based-reporting
Starting Evidence.dev development environment mounted on /evidence-workspace in the container.
Provided arguments => 
Running command => npm install && npm run dev -- --host 0.0.0.0

up to date, audited 555 packages in 8s

67 packages are looking for funding
  run `npm fund` for details

5 vulnerabilities (1 moderate, 4 high)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
npm notice 
npm notice New major version of npm available! 8.11.0 -> 9.2.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.2.0>
npm notice Run npm install -g npm@9.2.0 to update!
npm notice 

> my-evidence-project@0.0.1 dev
> evidence dev -o "--host" "0.0.0.0"


markroden@mmr-laptop:~/src/evidence/evidence-based-reporting$
which is a different version of npm than what I had above (8.11 vs 8.5), and I figured the docker would be more up to date/correct anyway, but I do not seem to have anything running on port 3000
b
I think in this situation (with docker) perhaps it doesnt run on localhost? I'm absolutely not a docker expert though
@lively-grass-48383 is likely to know more on the docker side
r
oh, I thought that was the point of the docker approach
running this to get a newer node version: `
Copy code
curl -fsSL <https://deb.nodesource.com/setup_18.x> | sudo -E bash -
`
fwiw
b
Did you use our docker repo instructinos for docker: https://github.com/evidence-dev/docker-devenv?
r
yes
b
To be honest, on the docker side, I'm more likely to mislead you than help!
r
kk
lemme see if I can get the node stuff up to date
👍🏼 1
b
the local npm install I think I should be able to help with!
🙏 1
r
I'll give it a shot
I have until 1pm locally 🙂
b
is that 17 mins?
r
looks like ubuntu -really- does not want me upgrading node very easily at all
yep
b
i recommend NVM
r
node version manager?
(I am not a js developer at all)
b
correct yeah
it allows you to have different version of node on your machine at once and swap between them
r
I figure it's like pyenv or the thing for java who's name escapes me at the moment (cobalt?)
now I've got
Copy code
TypeError: Cannot read properties of undefined (reading 'filter')
    at BreadCrumbs.svelte:34:26
    at Array.forEach (<anonymous>)
    at buildCrumbs (BreadCrumbs.svelte:33:15)
    at BreadCrumbs.svelte:41:16
    at Object.$$render (/home/markroden/src/evidence/evidence-based-reporting/node_modules/svelte/internal/index.js:1702:22)
    at eval (/@fs/home/markroden/src/evidence/evidence-based-reporting/node_modules/@evidence-dev/components/ui/Header.svelte:24:189)
    at Object.$$render (/home/markroden/src/evidence/evidence-based-reporting/node_modules/svelte/internal/index.js:1702:22)
    at eval (/src/pages/__layout.svelte:58:90)
    at Object.$$render (/home/markroden/src/evidence/evidence-based-reporting/node_modules/svelte/internal/index.js:1702:22)
    at root.svelte:36:36
b
That's progress
What does your package.json look like?
r
indeed! I'm on localhost:3000 to see the error
b
I'm interested in what version of evidence you have installed.
r
Copy code
{
  "name": "my-evidence-project",
  "version": "0.0.1",
  "scripts": {
    "build": "evidence build",
    "dev": "evidence dev -o",
    "test": "evidence build"
  },
  "engines": {
    "npm": ">=7.0.0",
    "node": ">=14.0.0"
  },
  "type": "module",
  "dependencies": {
    "@evidence-dev/evidence": "^5.0.2"
  }
}
b
yes it's an old version
r
this is straight from the template
ok, what do I do?
or rather, straight from the 'degit' command
b
bump that number to 6.0.2
in the package.json file
r
ok
b
and then npm install again
r
no need to repull? now that I have a newer version of node?
b
no the npm install process should do that for you
r
that mean the template package.json needs to be bumped?
b
yes, sorry
Copy code
{
  "name": "my-evidence-project",
  "version": "0.0.1",
  "scripts": {
    "build": "evidence build",
    "dev": "evidence dev -o",
    "test": "evidence build"
  },
  "engines": {
    "npm": ">=7.0.0",
    "node": ">=14.0.0"
  },
  "type": "module",
  "dependencies": {
    "@evidence-dev/evidence": "^6.0.2"
  }
}
r
no biggie, just wondering what happened
b
Is what I meant by 6.0.2
r
Copy code
markroden@mmr-laptop:~/src/evidence/evidence-based-reporting$ npm install

removed 1 package, changed 3 packages, and audited 554 packages in 9s

67 packages are looking for funding
  run `npm fund` for details

5 vulnerabilities (1 moderate, 4 high)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
that normal? 5 vulnerabilities?
b
it is right now, we're working on them! A couple of our dependencies need to be bumped
r
woot got it running!
🎉 2
b
LMK if you have any other issues!
r
will do, much appreciated!
😇 1
When I configure the snowflake connector, where does that information live? I don't want to check it in on accident
b
It lives in
./evidence/template/evidence.settings.json
, but is gitignored
r
👍