-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PhoneGap build in 1.2 #121
Comments
Yes, there is one extra requirement to get the npm build working in PhoneGap. Essentially there needs to be another window.WQ_CONFIG = {
router: {
base_url: getBaseUrl()
},
store: {
service: 'https://[SERVER_DOMAIN]',
defaults: {'format': 'json'}
}
} My plan was to release something like this as a fix to the project template in 1.2.1 (see wq/wq.create#6). However, it looks like PhoneGap Build itself will be discontinued a month from now (per https://build.phonegap.com/). Thus, I will instead be deprecating the Going forward, the recommendation will be to do one or both of the following:
|
- leverage collectstatic on app/ (fixes #6, fixes #21) - replace RequireJS build with ES modules (see wq/wq.app#111) - move --with-npm template to @wq/cra-template (in wq.start repo) - implement service worker (see wq/wq.app#63, wq/wq.app#107) - drop support for PhoneGap Build and Application Cache (see wq/wq.app#121)
- use collectstatic (see wq/wq-django-template#6 & wq/wq-django-template#21) - replace RequireJS build with ES modules (see wq/wq.app#111) - move --with-npm template to @wq/cra-template - implement service worker (see wq/wq.app#63, wq/wq.app#107) - drop support for PhoneGap Build and Application Cache (see wq/wq.app#121)
I just released wq.app 1.3 alpha, which includes a deprecation warning for the |
Hi there,
When we're building for phonegap via the
wq phonegap
command in the npm version of the tool, it doesn't appear to give us the expected output (in terms of the html file) in order to make the app work with PG.Previously we had an index file that looked similar to this:
The new output from
npm run build
looks like so:When we test the built npm files via
npx run serve
, the site behaves as expected. So the npm build process is working well. What I'm unsure of is - how do we go about ensuring that phonegap is being initialized correctly (do we need to do something similar to the previous template)? Does the npm generated index page require additional processing to add the required phonegap libraries etc?Related to: #119
The text was updated successfully, but these errors were encountered: