💡 Feature request

create-using-template supports creating dynamic files but not dynamic folders.

Is your feature request related to a problem? Please describe

We are using create-using-template generator to develop a template module to help some of legacy applications to OneApp V5. Since its international markets, each market team will use different locale(en-US, en-AU, ja-JP etc).
This locale information will be obtained from user via prompts and need to generate dynamic folder named as this value. This is required as per OneApp module structure in this one-app documentation

module
├── README.md
├── locale
| ├── en-US
| | ├── links
| | | └── production.json
| | | └── qa.json
| | | └── integration.json
| | └── copy.json
| └── es-mx
| ├── links
| | └── production.json
| | └── qa.json
| | └── integration.json
| └── copy.json
├── package.json
└── src
└── index.js

Describe the solution you'd like

We would like create-using-template to support dynamic folder creation similar to dynamic file creation.

Describe alternatives you've considered

The teams who may use our template module can rename the locale folder as per their need after the module generation is completed manually. But really not an ideal solution.

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

🐞 Bug Report

Describe the bug

When running a local template for testing purposes, the path to the template only works if it is relative to the current directory. Absolute paths give an error.

To Reproduce

1. Run npm pack in a template directory to create a tgz file.
2. Run npm init using-template /Users/me/workspace/some-template/some-template-1.0.0.tgz
3. Get error.

Failed to create module: Invalid or unexpected token
/Users/me/workspace/some-template/some-template-1.0.0.tgz:1
�
^
SyntaxError: Invalid or unexpected token
    at internalCompileFunction (node:internal/vm:73:18)
    at wrapSafe (node:internal/modules/cjs/loader:1178:20)

OTOH, if you pass a relative path to tgz from the current directory, it works as expected.

npm init using-template ../some-template/some-template-1.0.0.tgz`

Expected behavior

There should be no difference between absolute and relative paths.

System information

• OS: macOS
• Version of create-using-template: v1.11.0
• Node version: v18.18.2

🐞 Bug Report

Describe the bug

The npm install that is done in Step 5 uses the --prefer-offline flag to npm. While this is fast, it means your newly created project will have the same dependency versions as the last time you ran the generator, including any security issues. Best practice is to always use the current versions of packages when creating a new project. Otherwise you may start out with security vulnerabilities.

To Reproduce

Create a project using the template. The npm command will be run with --prefer-offline at the end.

Expected behavior

Either remove the flag or provide an option to not use it.