How do I avoid splitting the layout in a PWA project?

When you list the files that you want to cache with the Service Worker version, in most cases the style file is made available offline.

Changing the CSS may cause the application to suffer from the divergence and CSS of the "html / javascript" cache in production.

Even if you remove the CSS file from the cache list, this break may happen.

What solutions do you typically use in the PWA scenario or the best solution to avoid a layout change in a new PWA version?

For example, adding a query string if there is a high probability of break, and so on.

rest – The PWA workflow is denied access so that the API call retrieves allocations

I have an SPD 2013 workflow on our PWA site that has worked flawlessly for 6 months.
My colleague left the company and the administrator has disabled his 365 account.

Suddenly the workflow fails and the correct information is not retrieved.

I added e-mail commands to the workflow to send the contents of the dictionary variable immediately after the API call for assignments and to get:

{"error": {"code": "- 2147024891, Microsoft.Office.Project.Server.Exceptions.ProjectServerUnauthorizedAccessException", "message": {"lang": "en-US", "value": "Access denied. You do not have permission to perform this action or access this resource. "}}}

The workflow / e-mail is shown below:

Enter image description here

E-mail command

I have made sure that I am a website owner. I re-enabled my colleague's account as it was before he left, but it still fails.

The list workflow is now triggered when I was the initiator where my colleague was previously.

I'm not an API / workflow expert and can not figure out what I'm missing. Currently, this has implications that we can import project tasks into our SharePoint lists to engineer engineers.

Any ideas of what I need to do to get that working again would be very grateful.

Many thanks

vuejs2 – How to deal with analytics on PWA when deployed both as a web app and as an apk in the play store

How should I use analytics in one PWA Web App? If I add Analytics from Google Analytics to Webapp and publish it to a server, how should I track usage later if I want to publish it to the Google Play Store?

Here is the scenario:

  • I use that PWA from a subdomain.
  • then I publish the PWA from the Google Play Store as TWA,

My concerns:

Should I use the Google Analytics snippet for the web to track subdomain-based PWA and Firebase analytics for my Google Play Store app?


Can I track both versions at the same time with a single method?

I found this FAQ from Chrome Developer about using Google Analytics

The CPA Library follows the basic usage pattern of Google Analytics and is familiar to existing Google Analytics users. However, unlike Google Analytics' web-based official JavaScript libraries, the CPA library uses an "app-centric" model that works better with packaged apps. Among other things, the library provides methods for certain types of hits, such as event and appView, and can be used in both closure-based and traditional JavaScript projects.

I use Vuejs as a frontend with pwa Template, not sure if it applies to my use case. Any suggestion or any direction would be greatly appreciated.

pwa studio – How to set up a copy of Venia Concept to work locally

I'm into PWA Studio and I want to find out how easy it is to copy Venia-Concept and use it as a stand-alone REACT app. Instead of downloading the entire Monorepo containing all the other packages.

So far, I've tried it below, but an error is issued stating that Babel can not find it.

git clone venia-temp
cd venia-temp
CP -R packages / Venia concept ../
cp babel.config.js ../venia-concept/
cd ../venia-concept/
Install yarn
Build a yarn run

$ Yarn-thread clean && yarn-thread build: esm && yarn-thread validate-query && yarn-thread build: prod
$ rimraf dist esm
$ BABEL_ENV = Development babel src -out-dir esm -root-mode & up; & # 39; up; --source-maps --copy-files
/ bin / sh: babel: command not found
Error Command with exit code 127 failed.

Any ideas what causes this problem and how can I get it to work?

I know I could use the venia consumer example or fallback studio, but I'm interested in how it works.

When I run Add yarn Babel-Cli -D I pass the last mistake, but a new one comes …

Build $ yarn run
Yarn run v1.13.0
$ Yarn-thread clean && yarn-thread build: esm && yarn-thread validate-query && yarn-thread build: prod
$ rimraf dist esm
$ BABEL_ENV = Development babel src -out-dir esm -root-mode & up; & # 39; up; --source-maps --copy-files
SyntaxError: src / RootComponents / CMS / CMS.js: Unexpected token (6:15)
4 | Export standard class CMS extends the component {
5 | render () {
> 6 | return ;
| ^
7 | }
8 | }

Subdomain – Canonical URL of PWA – refer to maindomain?

We launch several versions of our PWA at the following URLs: (always refers to the latest stable version)

Our users start this version via our website:

All the* PWA pages have the canonical URL:

With the idea to link to these versions, the advantage is transferred to the main website.

Our website home page currently has the following two URLs: (english version) (french version)

My questions are:

  • Does it make sense to show the canonical URL on our homepage? Should we refer you to their respective release pages?
  • Should the canonical URL of the PWA refer to the / en version of the website? It will only be forwarded to / if the browser language is French

seo – Can I prevent the loading of HTML text and header in PWA when Javascript is enabled?

We have limited resources and can not use server-side technology on our website. We use PWA technology. What is our solution for pages indexed in Google?

Can we load some headers and body tags if js is off and prevent them from loading when js is enabled?

I read the John Guide:
But it is not clear what we can do if js is disabled and if js is enabled?

And there is also a contradiction to John's post in this link:

Google said you test your pages using the js-less browser and see if your site is reachable and viewable without js.

What should we finally do?