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
When using the 4.0 alpha, I cannot figure out a way to add a license key to the package.json file in the template. Therefore when I create a project with my create-react-app template it always gives me the "warning ../../package.json: No license field" warning. Please add the ability to add a license key in the template.json file of the templates or let me know if there is already a way to achieve this.
Steps to reproduce
(Write your steps here:)
Using the 4.0 alpha of create-react-app and a custom template, add license key in template.json
Create a project with your custom template
Run 'yarn start'
Expected behavior
To start up with no warnings and have a "license" key in the package.json file.
Actual behavior
It started up, but with the "warning ../../package.json: No license field" warning and does not have a "license" key in the package.json file.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.
Describe the bug
When using the 4.0 alpha, I cannot figure out a way to add a license key to the package.json file in the template. Therefore when I create a project with my create-react-app template it always gives me the "warning ../../package.json: No license field" warning. Please add the ability to add a license key in the template.json file of the templates or let me know if there is already a way to achieve this.
Steps to reproduce
(Write your steps here:)
Expected behavior
To start up with no warnings and have a "license" key in the package.json file.
Actual behavior
It started up, but with the "warning ../../package.json: No license field" warning and does not have a "license" key in the package.json file.
The text was updated successfully, but these errors were encountered: