Results 1 to 6 of 6

Thread: @sencha/[email protected] Causing Errors

  1. #1
    Sencha MVP Team Member
    Join Date
    Sep 2016
    Location
    Kennewick, WA
    Posts
    150

    Default @sencha/[email protected] Causing Errors

    I just installed the early access ExtAngular and ran through the documentation on Getting Started.

    Upon running npm start there were errors encountered. Here is a screenshot of the error.

    ExtAngularError.jpg

    Here is the error log
    Code:
    0 info it worked if it ends with ok
    1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
    1 verbose cli   'C:\\Users\\andrew.allord\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
    1 verbose cli   'run',
    1 verbose cli   'dev' ]
    2 info using [email protected]
    3 info using [email protected]
    4 verbose run-script [ 'predev', 'dev', 'postdev' ]
    5 info lifecycle @sencha/[email protected]~predev: @sencha/[email protected]
    6 info lifecycle @sencha/[email protected]~dev: @sencha/[email protected]
    7 verbose lifecycle @sencha/[email protected]~dev: unsafe-perm in lifecycle true
    8 verbose lifecycle @sencha/[email protected]~dev: PATH: C:\Users\andrew.allord\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\andrew.allord\Documents\Development\my-app\node_modules\.bin;C:\Users\andrew.allord\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\andrew.allord\Documents\Development\my-app\node_modules\.bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Users\andrew.allord\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Microsoft VS Code\bin;C:\Users\andrew.allord\bin\Sencha\Cmd\6.6.0.13;C:\Users\andrew.allord\AppData\Roaming\npm
    9 verbose lifecycle @sencha/[email protected]~dev: CWD: C:\Users\andrew.allord\Documents\Development\my-app
    10 silly lifecycle @sencha/[email protected]~dev: Args: [ '/d /s /c',
    10 silly lifecycle   'webpack-dev-server --env.verbose=no --env.environment=development  --env.browser=true  --env.watch=yes' ]
    11 silly lifecycle @sencha/[email protected]~dev: Returned: code: 1  signal: null
    12 info lifecycle @sencha/[email protected]~dev: Failed to exec dev script
    13 verbose stack Error: @sencha/[email protected] dev: `webpack-dev-server --env.verbose=no --env.environment=development  --env.browser=true  --env.watch=yes`
    13 verbose stack Exit status 1
    13 verbose stack     at EventEmitter.<anonymous> (C:\Users\andrew.allord\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
    13 verbose stack     at emitTwo (events.js:126:13)
    13 verbose stack     at EventEmitter.emit (events.js:214:7)
    13 verbose stack     at ChildProcess.<anonymous> (C:\Users\andrew.allord\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
    13 verbose stack     at emitTwo (events.js:126:13)
    13 verbose stack     at ChildProcess.emit (events.js:214:7)
    13 verbose stack     at maybeClose (internal/child_process.js:915:16)
    13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
    14 verbose pkgid @sencha/[email protected]
    15 verbose cwd C:\Users\andrew.allord\Documents\Development\my-app
    16 verbose Windows_NT 10.0.14393
    17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\andrew.allord\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
    18 verbose node v8.12.0
    19 verbose npm  v6.7.0
    20 error code ELIFECYCLE
    21 error errno 1
    22 error @sencha/[email protected] dev: `webpack-dev-server --env.verbose=no --env.environment=development  --env.browser=true  --env.watch=yes`
    22 error Exit status 1
    23 error Failed at the @sencha/[email protected] dev script.
    23 error This is probably not a problem with npm. There is likely additional logging output above.
    24 verbose exit [ 1, true ]
    How can one resolve this?
    Andy Allord
    Sencha MVP/Software Engineer

  2. #2
    Sencha - Forum Administrator
    Join Date
    Sep 2017
    Posts
    1,006

    Default

    Hi Andy,

    I just sent this over to the support team and asked them to get back with you to provide some help. Sorry for the inconvenience!

    Michele

  3. #3
    Sencha MVP Team Member
    Join Date
    Sep 2016
    Location
    Kennewick, WA
    Posts
    150

    Default

    Quote Originally Posted by Forum_Adm View Post
    Hi Andy,

    I just sent this over to the support team and asked them to get back with you to provide some help. Sorry for the inconvenience!

    Michele
    Thanks Michele..
    Andy Allord
    Sencha MVP/Software Engineer

  4. #4
    Sencha - Product Team
    Join Date
    Apr 2015
    Posts
    110

    Default

    We pushed updates to ExtAngular packages. Can you pl. retry? Thx!

    Quote Originally Posted by aallord View Post
    I just installed the early access ExtAngular and ran through the documentation on Getting Started.

    Upon running npm start there were errors encountered. Here is a screenshot of the error.

    ExtAngularError.jpg

    Here is the error log
    Code:
    0 info it worked if it ends with ok
    1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
    1 verbose cli   'C:\\Users\\andrew.allord\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
    1 verbose cli   'run',
    1 verbose cli   'dev' ]
    2 info using [email protected]
    3 info using [email protected]
    4 verbose run-script [ 'predev', 'dev', 'postdev' ]
    5 info lifecycle @sencha/[email protected]~predev: @sencha/[email protected]
    6 info lifecycle @sencha/[email protected]~dev: @sencha/[email protected]
    7 verbose lifecycle @sencha/[email protected]~dev: unsafe-perm in lifecycle true
    8 verbose lifecycle @sencha/[email protected]~dev: PATH: C:\Users\andrew.allord\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\andrew.allord\Documents\Development\my-app\node_modules\.bin;C:\Users\andrew.allord\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\andrew.allord\Documents\Development\my-app\node_modules\.bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Users\andrew.allord\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Microsoft VS Code\bin;C:\Users\andrew.allord\bin\Sencha\Cmd\6.6.0.13;C:\Users\andrew.allord\AppData\Roaming\npm
    9 verbose lifecycle @sencha/[email protected]~dev: CWD: C:\Users\andrew.allord\Documents\Development\my-app
    10 silly lifecycle @sencha/[email protected]~dev: Args: [ '/d /s /c',
    10 silly lifecycle   'webpack-dev-server --env.verbose=no --env.environment=development  --env.browser=true  --env.watch=yes' ]
    11 silly lifecycle @sencha/[email protected]~dev: Returned: code: 1  signal: null
    12 info lifecycle @sencha/[email protected]~dev: Failed to exec dev script
    13 verbose stack Error: @sencha/[email protected] dev: `webpack-dev-server --env.verbose=no --env.environment=development  --env.browser=true  --env.watch=yes`
    13 verbose stack Exit status 1
    13 verbose stack     at EventEmitter.<anonymous> (C:\Users\andrew.allord\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
    13 verbose stack     at emitTwo (events.js:126:13)
    13 verbose stack     at EventEmitter.emit (events.js:214:7)
    13 verbose stack     at ChildProcess.<anonymous> (C:\Users\andrew.allord\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
    13 verbose stack     at emitTwo (events.js:126:13)
    13 verbose stack     at ChildProcess.emit (events.js:214:7)
    13 verbose stack     at maybeClose (internal/child_process.js:915:16)
    13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
    14 verbose pkgid @sencha/[email protected]
    15 verbose cwd C:\Users\andrew.allord\Documents\Development\my-app
    16 verbose Windows_NT 10.0.14393
    17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\andrew.allord\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
    18 verbose node v8.12.0
    19 verbose npm  v6.7.0
    20 error code ELIFECYCLE
    21 error errno 1
    22 error @sencha/[email protected] dev: `webpack-dev-server --env.verbose=no --env.environment=development  --env.browser=true  --env.watch=yes`
    22 error Exit status 1
    23 error Failed at the @sencha/[email protected] dev script.
    23 error This is probably not a problem with npm. There is likely additional logging output above.
    24 verbose exit [ 1, true ]
    How can one resolve this?

  5. #5
    Sencha MVP Team Member
    Join Date
    Sep 2016
    Location
    Kennewick, WA
    Posts
    150

    Default

    Quote Originally Posted by sandeep.adwankar View Post
    We pushed updates to ExtAngular packages. Can you pl. retry? Thx!
    Just tried logging in to update and received the following error.

    Code:
    0 info it worked if it ends with ok
    1 verbose cli [ '/usr/local/bin/node',
    1 verbose cli   '/usr/local/bin/npm',
    1 verbose cli   'login',
    1 verbose cli   '--registry=https://sencha.myget.org/F/early-adopter/npm/',
    1 verbose cli   '[email protected]' ]
    2 info using [email protected]
    3 info using [email protected]
    4 verbose npm-session 811066954818bd06
    5 verbose web login before first POST
    6 http request → POST https://sencha.myget.org/F/early-adopter/npm/-/v1/login
    7 http 404 ← Not Found (https://sencha.myget.org/F/early-adopter/npm/-/v1/login)
    8 verbose web login not supported, trying couch
    9 verbose login before first PUT { _id: 'org.couchdb.user:aallord',
    9 verbose login   name: 'xxx',
    9 verbose login   password: 'XXXXX',
    9 verbose login   type: 'user',
    9 verbose login   roles: [],
    9 verbose login   date: '2019-02-08T04:08:39.622Z' }
    10 http request → PUT https://sencha.myget.org/F/early-adopter/npm/-/user/org.couchdb.user:xxx
    11 http 403 ← { "error": "Invalid login", "reason": "The specified login is not valid." } (https://sencha.myget.org/F/early-adopter/npm/-/user/org.couchdb.user:xxx)
    12 verbose adduser before first PUT { _id: 'org.couchdb.user:aallord',
    12 verbose adduser   name: 'xxxx',
    12 verbose adduser   password: 'XXXXX',
    12 verbose adduser   email: '[email protected]',
    12 verbose adduser   type: 'user',
    12 verbose adduser   roles: [],
    12 verbose adduser   date: '2019-02-08T04:08:40.071Z' }
    13 http request → PUT https://sencha.myget.org/F/early-adopter/npm/-/user/org.couchdb.user:xxx
    14 http 403 ← { "error": "Invalid login", "reason": "The specified login is not valid." } (https://sencha.myget.org/F/early-adopter/npm/-/user/org.couchdb.user:xxx)
    15 verbose stack Error: Registry returned 403 for PUT on https://sencha.myget.org/F/early-adopter/npm/-/user/org.couchdb.user:xxx: Invalid login
    15 verbose stack     at fetch.defaults.catch.then.then.result (/usr/local/lib/node_modules/npm/node_modules/npm-profile/index.js:376:13)
    15 verbose stack     at process._tickCallback (internal/process/next_tick.js:68:7)
    16 verbose statusCode 403
    17 verbose pkgid org.couchdb.user:xxx
    18 verbose cwd /Users/xxx/Documents/
    19 verbose Darwin 18.2.0
    20 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "login" "--registry=https://sencha.myget.org/F/early-adopter/npm/" "[email protected]"
    21 verbose node v10.14.2
    22 verbose npm  v6.4.1
    23 error code E403
    24 error Registry returned 403 for PUT on https://sencha.myget.org/F/early-adopter/npm/-/user/org.couchdb.user:xxx: Invalid login
    25 verbose exit [ 1, true ]
    Thanks Sandeep
    Andy Allord
    Sencha MVP/Software Engineer

  6. #6
    Sencha - Sales Team
    Join Date
    Feb 2012
    Location
    Fort Myers, Florida
    Posts
    42

    Default

    I believe the issue is that in Windows, it does not like the quotes (') around the environment variables in the package.json for the scripts. you can remove those. we have fixed that in 6.7.1 and we are current in testing for that version
    Marc Gusmano
    Sales Engineer
    Sencha Inc.

Similar Threads

  1. tooltip causing errors
    By netnutmike in forum Ext JS 6.x Q&A
    Replies: 2
    Last Post: 6 Jul 2017, 1:56 PM
  2. Function.interceptBefore causing errors
    By Csegota in forum Ext: Q&A
    Replies: 2
    Last Post: 20 Mar 2014, 8:43 AM
  3. new version of firefox causing errors
    By thenewmexican in forum Ext 3.x: Help & Discussion
    Replies: 2
    Last Post: 5 Oct 2009, 6:15 AM
  4. Ext.ux.notification extension causing errors in my app
    By vayumahesh in forum Ext 2.x: Help & Discussion
    Replies: 2
    Last Post: 5 Feb 2009, 8:33 AM
  5. All ext pages causing js errors when not called locally.
    By malkishua in forum Ext 1.x: Help & Discussion
    Replies: 7
    Last Post: 21 Apr 2007, 12:13 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •