I removed the original test site and replaced it with just the assets folder which over time will contain all the logos for the various frameworks.
The cypress tests were also removed since they were testing that demo site, and various dependencies for the demo site were also removed (e.g: babel, react, webpack).
Test plan
Tested use of the package in build-info to confirm that the logo property was being returned as expected
Tested use of package in netlify frontend to confirm that the framework detection logic still worked as expected.
I did this by running the front end project locally with framework-info linked, logging in and going to create a new site, selected a nextJS project, confirmed that the default build commands were populated and a message indicating that a NextJS project was detected appeared
A picture of a cute animal (not mandatory, but encouraged)
Summary
Related issue
I removed the original test site and replaced it with just the
assetsfolder which over time will contain all the logos for the various frameworks.The cypress tests were also removed since they were testing that demo site, and various dependencies for the demo site were also removed (e.g: babel, react, webpack).
Test plan
build-infoto confirm that thelogoproperty was being returned as expectedframework-infolinked, logging in and going to create a new site, selected a nextJS project, confirmed that the default build commands were populated and a message indicating that a NextJS project was detected appearedA picture of a cute animal (not mandatory, but encouraged)