Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

There was an error in @ng-toolkit/universal@1.1.4

See original GitHub issue

I’m submitting a…


[x] Bug report  
[ ] Feature request
[ ] Documentation issue or request

In package


[ ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[x] @ng-tookit/universal

Current behavior

+ @ng-toolkit/universal@1.1.4
updated 2 packages in 6.069s
Installed packages for tooling via npm.
Invalid regular expression flags
/MyAPP/Demo/node_modules/@ng-toolkit/_utils/index.js:381
            .replace(/([A-Za-z]+(\.[A-z]+\((.*?)\))*)/gs, `"$1"`));
                     ^

SyntaxError: Invalid regular expression flags
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:599:28)
    at Object.Module._extensions..js (module.js:646:10)
    at Module.load (module.js:554:32)
    at tryModuleLoad (module.js:497:12)
    at Function.Module._load (module.js:489:3)
    at Module.require (module.js:579:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/MyAPP/Demo/node_modules/@ng-toolkit/universal/src/index.js:4:18)

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment


Angular version: 6.0.3
Angular CLI: 6.0.7


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: v8.9.1
- Platform:  darwin x64 10.13.3
- npm: v5.6.0

Others:

Issue Analytics

State:
Created 5 years ago
Comments:10 (5 by maintainers)

Top GitHub Comments

1reaction

MdShuaibcommented, Jul 31, 2018

if you are using angular-cli: 6.1.1

Downgrade to lower version of angular-cli

npm uninstall -g @angular/cli npm cache verify npm install -g @angular/cli@6.0.8 ng add @ng-toolkit/universal

And it works for me!

0reactions

playgroundcommented, Oct 15, 2018

I’m getting this error, running ng cli 6.2.5

npm install --save @ng-toolkit/universal @1.1.41-beta.110 npm ERR! code E400 npm ERR! 400 Bad Request: @ng-toolkit/pwa@^1.1.40

Top Results From Across the Web

Will Angular 12 supports @ng-toolkit/universal and allow for ...

Next, I tried with the lower version 1.1.45, it shows the error as follows: No matching version found for @nguniversal/express-engine@~12.2.0.

@ng-toolkit/universal NPM | npm.io

Universal support for your Angular application Tweet. Star it and share with others! This is part of the @ng-toolkit project. Check main page...

@ng-toolkit/universal - npm

Start using @ng-toolkit/universal in your project by running `npm i @ng-toolkit/universal`. There are 2 other projects in the npm registry ...

angular-universal-pwa - Bountysource

i try to install "ng add @ng-toolkit/universal" on my angular 6 project but it give me following error.My project is in Angular 6...

@ng-toolkit/universal versions and peer dependencies

Version, Peer Dependency Versions. 1.1.0. 1.1.1. 1.1.3. 1.1.4. 1.1.5. 1.1.6. 1.1.7. 1.1.8. 1.1.9. 1.1.10. 1.1.11. 1.1.12. 1.1.13. 1.1.14. 1.1.16. 1.1.18.