some dependencies move from dependencies to devDependencies

[yoshinorin]

Description

Move some dependencies from dependencies to devDependencies in package.json

Reason

The devDependencies are just for development dependency that like gulp (task runner), babel (transpiler), etc...
It is similar to require and require-dev relationship in composer.json for PHP.

IMHO, it is better to separate them for developers.

Thank you :)

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
No Duplication information

[ildyria]

To be honest, I'm not sure it matters as we are just using node to compile our JS. 😅

[d7415]

To be honest, I'm not sure it matters as we are just using node to compile our JS. sweat_smile

That was my immediate reaction. If you're using this repo and aren't developing, you're doing it wrong!

[kamil4]

Well, some users may be using this repo simply to stay at the cutting edge of our development (say, to try out a proposed patch for a bug they reported). Does the split make sense then?

[d7415]

Well, some users may be using this repo simply to stay at the cutting edge of our development (say, to try out a proposed patch for a bug they reported). Does the split make sense then?

Do we even look in there? (aside from apple-touch-icon-* which should be in dist...)

[yoshinorin]

IMHO, if separate dependencies and devDependencies we can understand a little easier which packages affect application behavior. I think this is also useful when upgrading a package version.

Generally, We have to check & test application behavior when update the package's version. But, devDependencies are no need. Because devDependencies are just for development, not change the application behavior.

But, I cant come up with other advantages.

[ildyria]

(aside from apple-touch-icon-* which should be in dist...)

Actually they are in img/ and it is fixed with LycheeOrg/Lychee#721