Package Exports
- @vaadin/vaadin-development-mode-detector
- @vaadin/vaadin-development-mode-detector/vaadin-development-mode-detector.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@vaadin/vaadin-development-mode-detector) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Utility method for detecting that an application using Vaadin Elements is running in development mode
Running Tests
There are no automatic tests as the functionality depends on the host the code is run on (localhost vs others) and the bundling status.
To verify functionality:
- Run
npm install
- Run
bower install
- Run
npm start
- Open http://localhost:8081/test/index.html
- Verify that
mode
isdevelopment
(green) - Verify that
importIfDevelopmentMode
isrun
(green) - Open http://
<yourip>
:8081/test/index.html - Verify that
mode
isproduction
(orange) - Verify that
importIfDevelopmentMode
isignored
(orange) - Run
npm run start:prod
- Open http://localhost:8081/test/index.html
- Verify that
mode
isproduction
(orange) - Verify that
importIfDevelopmentMode
isignored
(orange) - Open http://
<yourip>
:8081/test/index.html- Verify that
mode
isproduction
(orange) - Verify that
importIfDevelopmentMode
isignored
(orange)
- Verify that