Improve nodejs example to show subdirectories sync

[ilyeshammadi]

I've updated the nodejs example to show the use of the undocumented folder/*** sync feature that syncs subdirectories. My changes consist of just placing the javascript files in multiple folders and to get the attention of the developer learning skaffold to pay attention when checking the skaffold.yaml file on the difference between the folder/** and folder/*** sync mechanisms.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[ilyeshammadi]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[codecov-io]

Codecov Report

Merging #2024 into master will increase coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2024      +/-   ##
==========================================
+ Coverage   55.96%   56.03%   +0.07%     
==========================================
  Files         173      175       +2     
  Lines        7566     7615      +49     
==========================================
+ Hits         4234     4267      +33     
- Misses       2928     2940      +12     
- Partials      404      408       +4

Impacted Files	Coverage Δ
pkg/skaffold/schema/validation/validation.go	100% <0%> (ø)	⬆️
pkg/skaffold/schema/versions.go	74.35% <0%> (ø)	⬆️
pkg/skaffold/build/kaniko/types.go
pkg/skaffold/build/kaniko/sources/localdir.go
pkg/skaffold/build/kaniko/sources/gcs.go
pkg/skaffold/build/kaniko/run.go
pkg/skaffold/build/kaniko/sources/sources.go
pkg/skaffold/build/kaniko/kaniko.go
pkg/skaffold/build/kaniko/secret.go
pkg/skaffold/build/kaniko/logs.go
... and 11 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9a68f2a...b4f4791. Read the comment docs.

[priyawadhwa]

This LGTM!

Looks like there is documentation around this feature, and skaffold.dev should be updated after the next release.

[priyawadhwa]

Whoops, one thing to fix -- could you make these changes in integration/examples/nodejs instead of examples/nodejs? The way we handle config changes requires this.

[ilyeshammadi]

@priyawadhwa should be fixed now!

[tejal29]

@Ilyes-Hammadi , can you make the change in both files? so they are in both dir
examples are served as user samples and integration/examples are tested

[ilyeshammadi]

@tejal29 The changes are now in both folders.

addressed comments