Problem with app scaffold

[matteyu]

Describe the bug
This is a three part problem

• when scaffolding a react app (following this doc https://docs.ignite.com/clients/react), there is a step to generating the hooks required for the app. One of the hooks generated useIbcApplicationsTransferV1 are riddled with errors due to =** being generated with the hash, trace and denom variables. Also, there is a left over unused import of vue (considering it's not part of the dependencies).

• scaffolding a vue application also results in the same errors above

• the generated ts-client for the client instance is generated outside of the scaffolded app. Therefore, it either needs to be linked using npm link (which needs to be done manually) or you transfer the ts-client directory that has been generated into the scaffolded app directory. If not done automatically, maybe good to add in docs for this step.

To reproduce
Steps to reproduce the behavior:

1. scaffold a react or vue application
2. generate hooks or composables
3. run npm install to get the deps
4. run npm run dev
5. application should fail to build/run due to errors noted in the bug section

What version are you using?

Ignite CLI version: v0.27.1

[clockworkgr]

Describe the bug This is a three part problem

• when scaffolding a react app (following this doc https://docs.ignite.com/clients/react), there is a step to generating the hooks required for the app. One of the hooks generated useIbcApplicationsTransferV1 are riddled with errors due to =** being generated with the hash, trace and denom variables. Also, there is a left over unused import of vue (considering it's not part of the dependencies).

• scaffolding a vue application also results in the same errors above

The "=**" issue should have been fixed with: #3592

I'll see if there was a regression of sorts.

Added a PR to remove the unnecessary type import here: #3631

• the generated ts-client for the client instance is generated outside of the scaffolded app. Therefore, it either needs to be linked using npm link (which needs to be done manually) or you transfer the ts-client directory that has been generated into the scaffolded app directory. If not done automatically, maybe good to add in docs for this step.

The user is notified of this when running npm run dev.
.
When you generate hooks (or composables in vue's case) the package.json in the react or vue template scaffold is modified to add a dependency to the generated ts-client pointing to file:xxxxxx in the local filesystem. Thus no need to run npm link.

The postinstall script (https://github.com/ignite/web/blob/develop/packages/react-template/postinstall.cjs ) will run npm install for the ts-client to ensure its own deps are present, while the prepare script (when running npm run dev: https://github.com/ignite/web/blob/develop/packages/react-template/prepare.cjs) lets you know that you're running with a local version of the ts-client that should eventually be published and the entry in package.json updated to reflect that.

To reproduce Steps to reproduce the behavior:

1. scaffold a react or vue application
2. generate hooks or composables
3. run npm install to get the deps
4. run npm run dev
5. application should fail to build/run due to errors noted in the bug section

What version are you using?

Ignite CLI version: v0.27.1