Error Running Dev on Linux

[TheConnMan]

I'm running into the following error after a fresh install on Ubuntu after running npm run dev:

ERROR in ./src/renderer/render.tsx
Module not found: Error: Can't resolve '@static/css/notable.min.css' in '/path/to/notable/src/renderer'
  @ ./src/renderer/render.tsx 37:0-37
  @ ./src/renderer/index.ts
  @ multi ./src/renderer/index.ts

ERROR in ./src/renderer/render.tsx
Module not found: Error: Can't resolve '@static/javascript/notable.min.js' in '/path/to/notable/src/renderer'
  @ ./src/renderer/render.tsx 38:0-43
  @ ./src/renderer/index.ts
  @ multi ./src/renderer/index.ts

Any help would be appreciated, even if the answer is just you don't do dev on Linux. Thanks.

[fabiospampinato]

It seems you forgot to run npm run svelto:dev first, which generates those files. Read here.

[gunt3001]

I'm getting the same errors. Running npm run svelto:dev or npm run svelto:prod doesn't seem to generate any files on my machine.

[dps]

I am also seeing the same error on MacOS X 10.14 having run npm run svelto:dev, its output was simply:

$ npm run svelto:dev

> notable@1.0.0 svelto:dev /Users/dps/notable
> svelto build --env development

[RomanKornev]

Running npm run svelto:dev produces The system cannot find the path specified. on Windows 10 x64 1803.

[TheConnMan]

I ran all the commands in the readme just in case this was necessary. I still got the same errors.

[dps]

If you also run npm install pacco it seems to work

[jcuenod]

Agreed, svelto:dev seems to need pacco.

[not that I can now run dev, however: I still haven't figured that out...]

[RomanKornev]

If anyone still has issues compiling:
Failed to load "notable\eyJicm93c2VycyI6WyJpZSA..." - just re-clone the repository again.

[jcuenod]

Shouldn't pacco be in package.json?

[fabiospampinato]

@jcuenod it's required by Svelto, which is package.json, and does define pacco in its package.json.

[jcuenod]

Hmm, well pacco didn't install when I ran npm install after pulling the latest. However, I can get notable running now (errors are still occurring though).

[fabiospampinato]

@jcuenod can you reproduce if you run npm i in a freshly cloned repo?

[jcuenod]

Nope, I'm having success now.
Thanks