[legacy-framework] remove typescript bits from package.json generated for js projects

[bcye]

Closes: blitz-js/legacy-framework#951

What are the changes and their implications?

• create two seperate files for JS and TS package.json (package.js.json and package.ts.json)
• rename the selected one to package.json during the generation process, discard the other

Checklist

• Tests added for changes (does this matter here? seems to be covered by existing ones)
• PR submitted to blitzjs.com for any user facing changes

[flybayer]

@bcye thanks so much! This solution would definitely work, but it would be better to only have a single package.json that has a few conditional changes based on whether it is JS or TS. Because with two package.json's, it will be easy for them to get out of sync.

@aem does our custom template engine support conditional checks in json files?

[flybayer]

Bump @aem

[flybayer]

@beerose looks good, but we should remove @types packages from js package.json. Once that's changed, you are good to merge without another check from me.

Also I remembered that we run tsc inside the husky pre-push hook. We need to remove that for JS version. Can do that as a separate PR though.

[beerose]

Also I remembered that we run tsc inside the husky pre-push hook. We need to remove that for JS version. Can do that as a separate PR though.

Yep! Will work on that in a separate pr

[blitzjs-bot]

Added @bcye contributions for code

[flybayer]

@bcye so sorry for the long delay on this!!! I was thinking we needed to make changes in our codegen process, but ultimately decided to just go with your original approach for now, even though there is some duplication we have to worry about.