vmasto / express-babel Goto Github PK

const person = { name: 'jasan', gender: 'Male' };
const tools = { computer: 'Mac', editor: 'sublime' };

const summary = {...person, ...tools};

nodemon crashes if I try to use the spread to combine the objects. Using _.merge instead.

It would be cool to have automatically linting when running npm run dev instead of actively starting it with npm run lint.

Dependabot can't resolve your Javascript dependency files.

As a result, Dependabot couldn't update any of your dependencies.

This could have been caused by a git reference having been deleted at the source, by an out-of-sync lockfile, or by a bug in Dependabot.

To help diagnose the issue, please try running an install locally. If no errors occur, get in touch and we'll help dig into it.

You can mention @dependabot in the comments below to contact the Dependabot team.

I saw the babel dependences was v6 which was too old and not recommend by official docs. I think it should be updated to v7 instead.

I am not able to understand that why dotenv is not working after building

In src/index.js, I am having the following code,

import path from 'path';
const envPath = path.resolve(__dirname, '../.env');

require('dotenv').config({ path: envPath});
import app from './app';

Now after running npm start, the .env file which is located in the root folder is not working, all the env variables are undefined. Am I missing something?

**Alternative ways **
These are the alternative ways I am using right now:

• docker-compose
• PM2 ecosystem.config.js

Hey, great work! I became a big fan of this starter kit. The only thing that didn't worked as expected were the breakpoints in vscode. I know the problem is somewhere in babel, but I have no clue about how to fix it. Do you? If you could be my tutor in this mission, I could try to fix it myself. :)

Congratz, one more time!

What do you think about:

https://github.com/babel/minify

to be added to script build? I'd open a merge request.