You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run yarn upgrade and try to build:
src/index.js → dist/NexusBridge.js...
[!] (plugin babel) Invariant Violation: [BABEL] C:\apps\siebel-nexus-bridge\packages\nexus-bridge\src\index.js: Invalid Option: The 'modules' option must be one of
'false' to indicate no module processing
a specific module type: 'commonjs', 'amd', 'umd', 'systemjs' - 'auto' (default) which will automatically select 'false' if the current
process is known to support ES module syntax, or "commonjs" otherwise
(While processing: "C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules\@babel\preset-env\lib\index.js")
src\index.js
Invariant Violation: [BABEL] C:\apps\siebel-nexus-bridge\packages\nexus-bridge\src\index.js: Invalid Option: The 'modules' option must be one of
'false' to indicate no module processing
a specific module type: 'commonjs', 'amd', 'umd', 'systemjs' - 'auto' (default) which will automatically select 'false' if the current
process is known to support ES module syntax, or "commonjs" otherwise
(While processing: "C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules\@babel\preset-env\lib\index.js")
at invariant (C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules\invariant\invariant.js:40:15)
at validateModulesOption (C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\preset-env\lib\normalize-options.js:129:26)
at normalizeOptions (C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\preset-env\lib\normalize-options.js:193:14)
at C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\preset-env\lib\index.js:228:37
at C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\helper-plugin-utils\lib\index.js:19:12
at C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\core\lib\config\full.js:199:14
at Generator.next ()
at Function. (C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\core\lib\gensync-utils\async.js:26:3)
at Generator.next ()
at evaluateSync (C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules\gensync\index.js:244:28)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ideaportriga/[email protected] build: yarn build:umd && yarn build:esm
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ideaportriga/[email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\OlegKoleskin\AppData\Roaming\npm-cache_logs\2020-06-04T07_48_52_647Z-debug.log
The text was updated successfully, but these errors were encountered:
Run yarn upgrade and try to build:
src/index.js → dist/NexusBridge.js...
[!] (plugin babel) Invariant Violation: [BABEL] C:\apps\siebel-nexus-bridge\packages\nexus-bridge\src\index.js: Invalid Option: The 'modules' option must be one of
process is known to support ES module syntax, or "commonjs" otherwise
(While processing: "C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules\@babel\preset-env\lib\index.js")
src\index.js
Invariant Violation: [BABEL] C:\apps\siebel-nexus-bridge\packages\nexus-bridge\src\index.js: Invalid Option: The 'modules' option must be one of
process is known to support ES module syntax, or "commonjs" otherwise
(While processing: "C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules\@babel\preset-env\lib\index.js")
at invariant (C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules\invariant\invariant.js:40:15)
at validateModulesOption (C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\preset-env\lib\normalize-options.js:129:26)
at normalizeOptions (C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\preset-env\lib\normalize-options.js:193:14)
at C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\preset-env\lib\index.js:228:37
at C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\helper-plugin-utils\lib\index.js:19:12
at C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\core\lib\config\full.js:199:14
at Generator.next ()
at Function. (C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules@babel\core\lib\gensync-utils\async.js:26:3)
at Generator.next ()
at evaluateSync (C:\apps\siebel-nexus-bridge\packages\nexus-bridge\node_modules\gensync\index.js:244:28)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ideaportriga/[email protected] build:
yarn build:umd && yarn build:esm
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ideaportriga/[email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\OlegKoleskin\AppData\Roaming\npm-cache_logs\2020-06-04T07_48_52_647Z-debug.log
The text was updated successfully, but these errors were encountered: