kibana/bin/kibana-plugin.bat

@echo off

SETLOCAL

set SCRIPT_DIR=%~dp0
for %%I in ("%SCRIPT_DIR%..") do set DIR=%%~dpfI

set NODE=%DIR%\node\node.exe
set NODE_ENV="production"

If Not Exist "%NODE%" (
  Echo unable to find usable node.js executable.
  Exit /B 1
)

TITLE Kibana Server

set "NODE_OPTIONS=--no-warnings %NODE_OPTIONS%" && "%NODE%" "%DIR%\src\cli_plugin" %*

:finally

ENDLOCAL
[pack installer] moved existing files into new structure 2016-03-03 19:44:43 +01:00			`@echo off`

			`SETLOCAL`

			`set SCRIPT_DIR=%~dp0`
			`for %%I in ("%SCRIPT_DIR%..") do set DIR=%%~dpfI`

			`set NODE=%DIR%\node\node.exe`
Always set NODE_ENV to production (#12010) Using the --dev flag is the only support way to change the internal Kibana environment to something else. Allowing NODE_ENV to be set at all can have unexpected results with our dependencies, so we now always set it to production. 2017-05-26 17:27:16 +02:00			`set NODE_ENV="production"`

[pack installer] moved existing files into new structure 2016-03-03 19:44:43 +01:00			`If Not Exist "%NODE%" (`
Create separate startup scripts for development and production (#13806) * Use separate startup scripts for development and production * build kibana directly * [build] Use downloaded node when pre-optimizing * clearer variable name * Add breaking changes docs 2017-11-22 19:49:37 +01:00			`Echo unable to find usable node.js executable.`
			`Exit /B 1`
[pack installer] moved existing files into new structure 2016-03-03 19:44:43 +01:00			`)`

			`TITLE Kibana Server`
Update node options Initialization on our scripts (#40302) * chore(NA): update node options initilization on our scripts * chore(NA): re-export NODE_OPTIONS instead of re-setting on vars * chore(NA): missing doc comment 2019-08-15 17:09:22 +02:00
			`set "NODE_OPTIONS=--no-warnings %NODE_OPTIONS%" && "%NODE%" "%DIR%\src\cli_plugin" %*`
[pack installer] moved existing files into new structure 2016-03-03 19:44:43 +01:00
			`:finally`

			`ENDLOCAL`