Adds deprecation notice if using Vite but have .js files when you should have .jsx

[cannikin]

Does a simple search for App.js, Routes.js, pages and components that have a .js extension. An app will have legitimate JS-only files with a .js extension so we don't search ALL of web/src. We also don't search the contents of the files for JSX tags, which may be overkill, and may slow down startup depending on how many files there are.

If the dev is seeing this error erroneously (because they have real JS-only files in web/src/pages or web/src/components it can be disabled with a REDWOOD_DISABLE_JS_DEPRECATION_NOTICE ENV var.

Questions

• Not sure if the text is really accurate: will .js files actually not work at all in 7.0.0, or will you just not have an optimal experience (like fast reload)?
• If .js files will technically still work, maybe this notice should be reworded to something about "recommend" and "optimal experience" and actually keep it forever, not remove it as of 7.0?

[cannikin]

@dac09 We could have this warning run during build as well, but that's most likely happening on a remove server and you won't actually see the output...

Unless we process.exit(1) and not even let the build complete? Maybe we save that for 7.0 if/when we make .jsx required.

[dac09]

Thanks Rob, leaving a couple of comments :)

[dac09]

@dac09 We could have this warning run during build as well, but that's most likely happening on a remove server and you won't actually see the output...

Unless we process.exit(1) and not even let the build complete? Maybe we save that for 7.0 if/when we make .jsx required.

Yeah I think on dev is enough. When we remove JSX-In-JS, It'll fail automatically (I think).

[cannikin]

Suggestions added, here's the new output:

Just need to coordinate so that either @jtoar names the codemod like that, or I update the output to match the real name.

[dac09]

or I update the output to match the real name.

Updated to match the codemod name!