AR.js | Efficient Augmented Reality for the Web - 60fps on mobile | Augmented Reality library

You need to update your vue-loader

Reason of the issue

It is expected browserslist to return an entry for each version ("safari 15.2", "safari 15.3") instead of a range ("safari 15.2-15.3"). So, this is just a bug in the parsing logic of Safari browser versions which needs to be corrected and will be done soon in fixed versions of Angular 12/Angular 13. Link to details is here.

IMPORTANT UPDATE:

This is fixed in v12.2.16 and v13.2.1, please update if you are experiencing this issue. Users on v11 shouldn't be affected. Link to details is here. If you can not/do not want to update for any reason, then one of the workarounds below can be used.

Workarounds:

Modify .browserslistrc

Add to .browserslistrc such lines:

Just remove the "extractCss": true from your production environment, it will resolve the problem.

The reason about it is extractCss is deprecated, and it's value is true by default. See more here: Extracting CSS into JS with Angular 11 (deprecated extractCss)

You can tested it easily. Put console.log(1) in the index.html, and console.log(2) in main.ts. First console will be 1, so index.html runs first.

When application is opened, initially index.html start to render and it will render with empty - because Angular app is still to be loaded (you can test that easily with CRTL + U - that is initial content that browser see). That was the big bottleneck for the SEO of SPA apps.

Once the Angular app is loaded, it will dynamically populate the content to the of the index.html.

UPDATE

I missed the part why the error is not thrown when index.html comes to tag. @Ashish explained that really well in his answer (and definitely deserves an upvote), so I will just quote his answer here:

Reason is, index.html is not an Angular template file, it is pure html, you can place any element inside it and it will never throw an error. But for Angular template files, during compile time it checks if is defined or not and throws compile time error if not defined.

Well, ItemCounterContext is important for this problem, just ignore StoreContext, it's for images... Here is a reducer function.

From v13 angular doesn't use tslint anymore due to deprecation.

Run ng add @angular-eslint/schematics to add eslint to your application.

It will use tslint-to-eslint-config to migrate you to eslint automatically.

It will generate a .eslintrc.json file and migrate tslint.json to it.

Nothing else is needed to be done.

ngx-build-plus too needs to be upgrade to the matching Angular version (i.e. 13).

First of all, if you want only 1 item selected at a time, then use instead of .

You are using the general sibling combinator ~ :

The general sibling combinator (~) separates two selectors and matches all iterations of the second element, that are following the first element (though not necessarily immediately), and are children of the same parent element.

If you want to change the color of the label associated with a radio, you need to place the radio before its label.

It can be done with a single rule :

In case you're using a service worker (eg @angular/pwa which installs @angular/service-worker along), you're entire angular app is being cached by the browser. This includes index.html + all javascript files + all stylesheets.

To have a new version of your application pushed to your users, you have to do 2 things:

Update your ngsw-config.json on each new release: