:host-context([dir=rtl]) .ion-float-start -> subselects_1.subselects[name] is not a function

Ionic Framework
#1

Hi, somebody with the same issue?

:host-context([dir=rtl]) .ion-float-start → subselects_1.subselects[name] is not a function

I migrate from angular 11 to 14, my project compile but something happen when build solution.

ionic build

ng run app:build
:heavy_check_mark: Browser application bundle generation complete.
:heavy_check_mark: Copying assets complete.
⠋ Generating index html…10 rules skipped due to selector errors:
:host-context([dir=rtl]) .ion-float-start → subselects_1.subselects[name] is not a function
:host-context([dir=rtl]) .ion-float-end → subselects_1.subselects[name] is not a function
:host-context([dir=rtl]) .ion-float-sm-start → subselects_1.subselects[name] is not a function
:host-context([dir=rtl]) .ion-float-sm-end → subselects_1.subselects[name] is not a function
:host-context([dir=rtl]) .ion-float-md-start → subselects_1.subselects[name] is not a function
:host-context([dir=rtl]) .ion-float-md-end → subselects_1.subselects[name] is not a function
:host-context([dir=rtl]) .ion-float-lg-start → subselects_1.subselects[name] is not a function
:host-context([dir=rtl]) .ion-float-lg-end → subselects_1.subselects[name] is not a function
:host-context([dir=rtl]) .ion-float-xl-start → subselects_1.subselects[name] is not a function
:host-context([dir=rtl]) .ion-float-xl-end → subselects_1.subselects[name] is not a function
:heavy_check_mark: Index html generation complete.

Ionic:

Ionic CLI : 6.20.1 (/usr/local/lib/node_modules/@ionic/cli)
Ionic Framework : @ionic/angular 6.2.9
@angular-devkit/build-angular : 14.2.2
@angular-devkit/schematics : 14.2.2
@angular/cli : 14.2.2
@ionic/angular-toolkit : 7.0.0

Capacitor:

Capacitor CLI : 4.2.0
@capacitor/android : 2.5.0
@capacitor/core : 4.2.0
@capacitor/ios : 2.5.0

Utility:

cordova-res : not installed globally
native-run (update available: 1.7.1) : 1.7.0

System:

NodeJS : v16.17.1 (/usr/local/bin/node)
npm : 8.15.0
OS : macOS Monterey

1 Like
#2

This is ok to ignore. What’s happening is angular is trying to analyze the CSS needed for your first route and inline it to the index.html. If it comes across css that it can’t understand, it will just print this warning and skip it. This is typically fine as the css isn’t removed, just skipped for inlining.

1 Like