Skip to content

Unable to build with latest updated version 3.4.4 #3896

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
gohelkiran30 opened this issue Nov 13, 2017 · 9 comments
Closed

Unable to build with latest updated version 3.4.4 #3896

gohelkiran30 opened this issue Nov 13, 2017 · 9 comments

Comments

@gohelkiran30
Copy link

Just downloaded the latest version and trying to create a build after removing topbar module but its getting failed.
Attached npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle [email protected]prebuild: [email protected]
6 silly lifecycle [email protected]
prebuild: no script for prebuild, continuing
7 info lifecycle [email protected]build: [email protected]
8 verbose lifecycle [email protected]
build: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]build: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/kiran/Downloads/swagger-ui-master/node_modules/.bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/kiran/.local/bin:/home/kiran/bin
10 verbose lifecycle [email protected]
build: CWD: /home/kiran/Downloads/swagger-ui-master
11 silly lifecycle [email protected]build: Args: [ '-c',
11 silly lifecycle 'npm run build-core && npm run build-bundle && npm run build-standalone' ]
12 silly lifecycle [email protected]
build: Returned: code: 1 signal: null
13 info lifecycle [email protected]~build: Failed to exec build script
14 verbose stack Error: [email protected] build: npm run build-core && npm run build-bundle && npm run build-standalone
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:920:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
15 verbose pkgid [email protected]
16 verbose cwd /home/kiran/Downloads/swagger-ui-master
17 error Linux 4.12.14-200.fc25.x86_64
18 error argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
19 error node v6.11.3
20 error npm v3.10.10
21 error code ELIFECYCLE
22 error [email protected] build: npm run build-core && npm run build-bundle && npm run build-standalone
22 error Exit status 1
23 error Failed at the [email protected] build script 'npm run build-core && npm run build-bundle && npm run build-standalone'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the swagger-ui package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error npm run build-core && npm run build-bundle && npm run build-standalone
23 error You can get information on how to open an issue for this project with:
23 error npm bugs swagger-ui
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls swagger-ui
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Q A
Bug or feature request? Bug
Which Swagger/OpenAPI version? 3.4.4
Which Swagger-UI version? 3.4.4
How did you install Swagger-UI? Download Zip
Which browser & version?
Which operating system?

Demonstration API definition

your: "API definition goes here"

Configuration (browser query string, constructor, config.yaml)

{
  "your": { "constructorConfig": "here" }
}

?yourQueryStringConfig=here

Expected Behavior

Current Behavior

Possible Solution

Context

@hkosova
Copy link
Contributor

hkosova commented Nov 13, 2017

FYI if you just need to remove the Topbar, an easier way is to change dist\index.html as follows:

  // Build a system
  const ui = SwaggerUIBundle({
    url: "http://petstore.swagger.io/v2/swagger.json",
    dom_id: '#swagger-ui',
    deepLinking: true,
    presets: [
      SwaggerUIBundle.presets.apis
    ]
  })

There's no need to rebuild the code in this case.

Credit goes to @shockey - #3229 (comment).

@heldersepu
Copy link
Contributor

@hkosova I just tried that modification to the index...
and there is a message that flashes:
<h4 data-reactroot="">No spec provided.</h4>
before we get to see the swagger-ui.

Another option that I've been using it is to just hide it using CSS:
.topbar {display:none}

@hkosova
Copy link
Contributor

hkosova commented Nov 13, 2017

@gohelkiran30 did you npm install before npm run build?

@shockey
Copy link
Contributor

shockey commented Nov 13, 2017

@heldersepu, are you providing a url parameter? If you don't provide a url, the UI doesn't have anything to do.

I see what you're describing with the latest if I omit the default url: "http://petstore.swagger.io/v2/swagger.json", in dist/index.html.

@heldersepu
Copy link
Contributor

heldersepu commented Nov 13, 2017

@shockey Yes I did, I changed the index.html exactly as suggested by @hkosova
I just test it, if there is no URL the message would stay, not just flash like I mentioned

@heldersepu
Copy link
Contributor

@shockey
Copy link
Contributor

shockey commented Nov 13, 2017

@heldersepu, thanks, looking now.


@gohelkiran30, we've seen this error before (in #2845, #3027, #3153) - in all cases, the problem was different, so this particular stack trace is not helpful... thanks, npm 😄

Some questions for you:

  • Did you run npm install before running npm run build?
  • What OS are you using? You left that Q&A section blank.

As seen in #3027, this can be an OS-specific problem.

@shockey
Copy link
Contributor

shockey commented Nov 13, 2017

@heldersepu, ah, I see what you're saying now, the message flashes. Sorry, I missed that in your original comment!

Let's move this discussion out of this issue - I'll open a new ticket in a moment.

@gohelkiran30
Copy link
Author

it was npm install issue
thanks all

@lock lock bot locked and limited conversation to collaborators Jul 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants