You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose adding support for customizable package.json templates in Glee projects. This enhancement will allow users to specify and use their own package.json configurations during project creation, significantly streamlining the setup process and improving the overall user experience.
How will this change help?
Current Behavior:
Currently, Glee generates a package.json file with default settings when a new project is created. Users then need to manually edit this file to adjust dependencies, scripts, and other settings to match their specific project requirements. Below is an example of the default package.json provided:
Introduce a feature to specify a custom package.json template during project creation. This can be achieved via a command-line option or configuration file, allowing users to predefine their project setup and avoid manual modifications. Below is an example of how users might set up their custom package.json:
Streamlined Setup: Avoids the need to manually edit a default package.json, making the project creation process faster and more user-friendly. Enhanced Customization: Users can start with a package.json file that meets their specific needs, reducing the need for post-creation adjustments. Improved Consistency: Ensures uniform configuration across multiple projects or teams by using predefined templates. Increased Efficiency: Automates the inclusion of standard dependencies, scripts, and settings, saving time and effort.
Screenshots
No response
How could it be implemented/designed?
Template Handling: Allow users to specify and apply a custom package.json template when creating a project, or use a default template if none is provided.
Placeholder Replacement: Support dynamic placeholders in the template (e.g., {projectName}, {version}) and replace them with user-provided values.
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Why do we need this improvement?
I propose adding support for customizable package.json templates in Glee projects. This enhancement will allow users to specify and use their own package.json configurations during project creation, significantly streamlining the setup process and improving the overall user experience.
How will this change help?
Current Behavior:
Currently, Glee generates a package.json file with default settings when a new project is created. Users then need to manually edit this file to adjust dependencies, scripts, and other settings to match their specific project requirements. Below is an example of the default package.json provided:
Proposed Enhancement:
Introduce a feature to specify a custom package.json template during project creation. This can be achieved via a command-line option or configuration file, allowing users to predefine their project setup and avoid manual modifications. Below is an example of how users might set up their custom package.json:
Benefits:
Streamlined Setup: Avoids the need to manually edit a default package.json, making the project creation process faster and more user-friendly.
Enhanced Customization: Users can start with a package.json file that meets their specific needs, reducing the need for post-creation adjustments.
Improved Consistency: Ensures uniform configuration across multiple projects or teams by using predefined templates.
Increased Efficiency: Automates the inclusion of standard dependencies, scripts, and settings, saving time and effort.
Screenshots
No response
How could it be implemented/designed?
Template Handling: Allow users to specify and apply a custom package.json template when creating a project, or use a default template if none is provided.
Placeholder Replacement: Support dynamic placeholders in the template (e.g., {projectName}, {version}) and replace them with user-provided values.
🚧 Breaking changes
Yes
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: