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
Currently, running dojo build -s just starts a web server that blindly serves the output directory for the current mode (e.g., /output/dev). However, this does not work for --mode=test as there are only two files there (functional.js and unit.js), and does not allow anything but the hash router to be used in other modes.
For dev and dist modes, one solution is to serve all extension-less routes from / and continue delivering assets (JS, CSS, HTML, images) statically. For test mode, we could attempt to serve node_modules/intern/index.html, but I am inclined to think that running tests is the purview of @dojo/cli-test-intern and that --serve should be disabled in test mode.
The text was updated successfully, but these errors were encountered:
Currently, running
dojo build -s
just starts a web server that blindly serves the output directory for the current mode (e.g.,/output/dev
). However, this does not work for--mode=test
as there are only two files there (functional.js
andunit.js
), and does not allow anything but the hash router to be used in other modes.For
dev
anddist
modes, one solution is to serve all extension-less routes from/
and continue delivering assets (JS, CSS, HTML, images) statically. Fortest
mode, we could attempt to servenode_modules/intern/index.html
, but I am inclined to think that running tests is the purview of@dojo/cli-test-intern
and that--serve
should be disabled intest
mode.The text was updated successfully, but these errors were encountered: