chore: max-statements warning in src/cli/init/index.ts

[tamirazrab]

Description

...

End to End Test:
(See Pepr Excellent Examples)

Related Issue

Fixes #1693

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Unit, Journey, E2E Tests, docs, adr added or updated as needed
• Contributor Guide Steps followed

[samayer12]

Thanks for the PR! While reviewing, I noticed that genPeprTS() wasn't actually doing anything that couldn't be solved by referencing a const. So, as a bonus, the refactored setupProjectStructure() function only requires two input parameters.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.08%. Comparing base (7a787b9) to head (e09476a).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1729      +/-   ##
==========================================
+ Coverage   82.05%   82.08%   +0.03%     
==========================================
  Files          52       52              
  Lines        2212     2211       -1     
  Branches      470      470              
==========================================
  Hits         1815     1815              
+ Misses        368      367       -1     
  Partials       29       29              

Files with missing lines	Coverage Δ
src/cli/init/templates.ts	72.72% <100.00%> (+2.13%)	⬆️

[tamirazrab]

Thanks for the PR! While reviewing, I noticed that genPeprTS() wasn't actually doing anything that couldn't be solved by referencing a const. So, as a bonus, the refactored setupProjectStructure() function only requires two input parameters.

Looks much clean now.

[cmwylie19]

Something is not getting generated during the npx pepr build -i pepr:dev as CI is not passing for 2 jobs consistently

This needs a little investigation

https://github.com/defenseunicorns/pepr/actions/runs/13012979379/job/36295073948?pr=1729

One way to test the build is create the pepr test module:

pepr $> npm test

When the pepr-test-module directory is created you can test the build. This allows you to step through the build code and make sure the dist folder is there with the correct files. I will try to find some time to look into this too very soon because I am not sure why the code I am seeing may not be generating some build artifact

pepr/pepr-test-module $> npx ts-node ../src/cli.ts build