Skip to content

fix(admin-ui): unable to launch admin-ui #1493

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

Closed
manojs1978 opened this issue Dec 6, 2023 · 3 comments · Fixed by #1495
Closed

fix(admin-ui): unable to launch admin-ui #1493

manojs1978 opened this issue Dec 6, 2023 · 3 comments · Fixed by #1495
Assignees
Labels
bug Something isn't working comp-admin-ui Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality

Comments

@manojs1978
Copy link
Contributor

Describe the bug
unable to launch admin-ui

To Reproduce
Steps to reproduce the behavior:

  1. install flex 5.0.0-21.nightly
  2. launch adminui
  3. See error

Expected behavior
should able to launch admin

Screenshots
If applicable, add screenshots to help explain your problem.
image

Desktop (please complete the following information):

  • OS: ubuntu
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]
    -flex 5.0.0-21.nighlty
    DB mysql

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@manojs1978 manojs1978 added the bug Something isn't working label Dec 6, 2023
@mo-auto mo-auto added comp-admin-ui Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality labels Dec 6, 2023
@duttarnab
Copy link
Contributor

Error log:

07:06:14 12/06/23 
> [email protected] build:prod
> node ./build/cli-tools.js --clear dist --create dist && webpack --config ./build/webpack.config.client.prod.js

Cleared target directory: /opt/jans/jans-setup/flex/dist
Created target directory: /opt/jans/jans-setup/flex/dist
assets by status 6.54 MiB [cached] 35 assets
Entrypoint app = 647.bundle.js app.css app.bundle.js 11 auxiliary assets
orphan modules 12.2 MiB (javascript) 559 bytes (css/mini-extract) 10.1 KiB (runtime) [orphan] 12986 modules
runtime modules 8.67 KiB 18 modules
built modules 12.8 MiB (javascript) 612 KiB (css/mini-extract) [built]
  modules by path ./node_modules/ 9.34 MiB 1340 modules
  modules by path ./plugins/ 1.53 MiB 266 modules
  modules by path ./app/ 1.04 MiB (javascript) 612 KiB (css/mini-extract)
    javascript modules 1.04 MiB 117 modules
    css modules 612 KiB 8 modules
  modules by path ./jans_config_api/dist/ 945 KiB 113 modules
  asset modules 5.52 KiB
    data:image/svg+xml,%3csvg xmlns=%27.. 324 bytes [built] [code generated]
    + 19 modules
  + 4 modules

ERROR in ./plugins/auth-server/components/Configuration/ConfigPage.js 21:0-51
Module not found: Error: Can't resolve '../../../../configApiSpecs.yaml' in '/opt/jans/jans-setup/flex/plugins/auth-server/components/Configuration'
resolve '../../../../configApiSpecs.yaml' in '/opt/jans/jans-setup/flex/plugins/auth-server/components/Configuration'
  using description file: /opt/jans/jans-setup/flex/package.json (relative path: ./plugins/auth-server/components/Configuration)
    Field 'browser' doesn't contain a valid alias configuration
    using description file: /opt/jans/jans-setup/flex/package.json (relative path: ./configApiSpecs.yaml)
      no extension
        Field 'browser' doesn't contain a valid alias configuration
        /opt/jans/jans-setup/flex/configApiSpecs.yaml doesn't exist
      .js
        Field 'browser' doesn't contain a valid alias configuration
        /opt/jans/jans-setup/flex/configApiSpecs.yaml.js doesn't exist
      .json
        Field 'browser' doesn't contain a valid alias configuration
        /opt/jans/jans-setup/flex/configApiSpecs.yaml.json doesn't exist
      .wasm
        Field 'browser' doesn't contain a valid alias configuration
        /opt/jans/jans-setup/flex/configApiSpecs.yaml.wasm doesn't exist
      as directory
        /opt/jans/jans-setup/flex/configApiSpecs.yaml doesn't exist
 @ ./plugins/ sync ^.*$
 @ ./plugins/PluginReducersResolver.js 24:84-108
 @ ./app/redux/store/index.js 9:0-53 32:0-7
 @ ./app/components/App/AppMain.js
 @ ./app/components/App/index.js 1:0-32 2:15-22
 @ ./app/index.js 4:0-33 12:90-93

webpack 5.89.0 compiled with 1 error in 228246 ms

@duttarnab
Copy link
Contributor

@jv18creator can we pull FeatureFlags from the generated OpenApi client.. so that we can avoid using configApiSpecs.yaml (which is not checked-in GH repo).
image

@jv18creator
Copy link
Contributor

jv18creator commented Dec 6, 2023

@duttarnab I couldn't find endoint to fetch featureFlags from jans_config_api docs.
Perhaps we could fetch AppConfiguration from spec url. I'll start with development.

jv18creator added a commit that referenced this issue Dec 7, 2023
duttarnab added a commit that referenced this issue Dec 7, 2023
fix(admin-ui): unable to launch admin-ui #1493
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working comp-admin-ui Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants