Currently, we skip the ...rw ts-to-js command in the current E2E tests, which is good for testings a TS project. However, since this is a critical path and the default for new project installation, it seems to me we should include it. And I don't believe the E2E tests will differ based on project being TS or JS, will it?
A simple way would be to change this line by removing --no-javascript flag:
https://github.com/redwoodjs/redwood/blob/5dbb9e0a87bde6fbfac391202ca4417fc7023aeb/tasks/run-e2e#L43
Is there reason to not do this here? If so, where else could we add the test?
Currently, we skip the
...rw ts-to-jscommand in the current E2E tests, which is good for testings a TS project. However, since this is a critical path and the default for new project installation, it seems to me we should include it. And I don't believe the E2E tests will differ based on project being TS or JS, will it?A simple way would be to change this line by removing
--no-javascriptflag:https://github.com/redwoodjs/redwood/blob/5dbb9e0a87bde6fbfac391202ca4417fc7023aeb/tasks/run-e2e#L43
Is there reason to not do this here? If so, where else could we add the test?