start-dev launch option (ts-node-dev)

[GrayStrider]

allows to work on project without re-building each time

[peterblazejewicz]

If accepted, it would require solution for serving static assets from public directory. At the moment, content usually pre-built like css (from scss) could not be used when started in that mode.
For example such minimal change does the trick, but is just a pointer on how to achieve this, could be better one:

• add cross-env as dev dependency

"start-dev": "cross-env NODE_ENV=development dotenv -- nodemon -e ts -x ts-node --files src/server.ts"

app.ts:

const staticAssetsRoot = (process.env.NODE_ENV === "development") ?
    path.join(__dirname, "../dist") :
    __dirname;

app.use(
    express.static(path.join(staticAssetsRoot, "public"), { maxAge: 31557600000 })
);

[GrayStrider]

If accepted, it would require solution for serving static assets from public directory. At the moment, content usually pre-built like css (from scss) could not be used when started in that mode.

@peterblazejewicz
I just launched it and everything seems to work fine? No unresolved resources or anything, css seems to be built as well.

perhaps, --files option takes care of things? Could someone test it and see what exactly doesn't work, if anything?

[GrayStrider]

Nevermind, found a much better option, one sec

[GrayStrider]

takes a few seconds to reload after changes, unlike nodemon;
--watch views will also trigger reload on any change in views folder (still need to refresh the page to see them)
unfortunatelly, couldn't make it trigger refresh on scss changes in public folder (--watch public,views), works when putting scss in views folder though.

[GrayStrider]

Are there any other adjustments needs to be made?

[anthony-bernardo]

why this is not merged ? this is a must have when you are working on a project