Run npm run start:pwa
to start the project in development mode.
Run npm run build:pwa -- -p && npm run serve:pwa -- -p
to start the project in production mode.
Server starts in http://localhost:3000
by default.
You should pass some queries to configure the server.
Use http://localhost:3000?siteId=XXX
to specify the site.
Use http://localhost:3000?ssrUrl=http://domain.com
to specify the SSR server.
Use http://localhost:3000?staticUrl=http://domain-static.com
to specify the Static server.
Use http://localhost:3000?server=http://domain.com
to specify both the SSR and the Static servers.
If you don't pass any server, a dynamic path ('/'
) will be used.
Use http://localhost:3000?env=prod
to specify a prod
(production) environment. If you don't pass it, then pre
is used.
This sets MODE
to pwa
:
npm run start:pwa
And this sets MODE
to amp
:
npm run start:amp
You can also pass --pwa
or --amp
to npm run start
:
npm run start -- --pwa
or npm run start -- --amp
You can also set MODE=amp
or MODE=pwa
in the environment variables.
Default NODE_ENV
is development
.
This sets NODE_ENV
to production
:
npm run start:pwa -- --prod
or npm run start:pwa -- -p
Default Express server is http://localhost:3000
.
This starts Express server on https://localhost:3000
:
npm run start:pwa -- --https
or npm run start:pwa -- -s
This starts node in debug mode:
npm run start:pwa -- --debug
or npm run start:pwa -- -d
Default Express port is 3000
.
This starts the server in a different port:
npm run start:pwa -- --port XXXX
This setting is for HMR only. You should use the static
query to set the public path dynamically.
This sets Webpack's HMR path (__webpack_hmr
) to http://localhost:3000
or https://localhost:3000
(depending on your http/https configuration):
npm run start:pwa -- --wp
or npm run start:pwa -- -w
This setting is for HMR only. You should use the static
query to set the public path dynamically.
This sets Webpack's HMR path (__webpack_hmr
) to a custom path:
npm run start:pwa -- --hmr https://ngrok.io/xxx
If you want to analyze the bundles, you can pass:
npm run start:pwa -- --analyze
or npm run start:pwa -- -a
The output html
files will be located in the .build/pwa/(client|server)/analyze
folders.
- Fix Lazy load in ads
- Lazy load is an option on ads
- Add scrollTop to template
- Fixes react-icon and ad reducers in AMP
- Add sticky code to ads
- Updated mobx-react version
- Add version to JS
- Update lazyload
- Fix title used in AMP Analytics
- Fix but on previous bug fix
- Fix anaylitics sending wrong title
- Fixes customDimensions store in analytics
- Update emotion
- Change slots to fills
- Start moving ads to its own package using slots
- Fixes to iframes package
- Fixes to some prop types
- iOS bug fixes of new connection
- More refactoring and bug fixes of new connection
- Refactor MST implementation
- New connection
- Load scripts on DOM load
- Import analytics dependencies from theme
- Go back to initialUrl
- Fix React dead code elimination warning
- Add Comscore to AMP
- Add initialUri compatibility (for wp-pwa-plugin >= 1.3.0)
- Fixes on GTM
- Configure Babel to support Chrome >= 40
- Add iFrames and CustomCSS extensions
- Check if ga is a function
- Add custom_dimensions in analytics
- Remove line
- Fix on virtualEvents
- Fix on virtualPageView
- Analytics package refactoring
- Start sending analytic events
- Use our analytics for development
- Fix comScore events
- Add analytic events
- Remove system
- Fix title in virtualPageView
- Update analytics db schema
- Add jest to eslint globals
#### 1.1.1
- Text deploy
#### 1.1.0
- Start versioning