Skip to content

uri.match is not a function after webpack update #1910

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
RicardoVaranda opened this issue Aug 31, 2016 · 4 comments
Closed

uri.match is not a function after webpack update #1910

RicardoVaranda opened this issue Aug 31, 2016 · 4 comments

Comments

@RicardoVaranda
Copy link
Contributor

RicardoVaranda commented Aug 31, 2016

Please provide us with the following information:

  1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
    Ubuntu 16.04
  2. Versions. Please run ng --version. If there's nothing outputted, please run
    in a Terminal: node --version and paste the result here:
angular-cli: 1.0.0-beta.11-webpack.8
node: 6.3.1
os: linux x64
  1. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.
    Updated from beta 10 to angular-cli webpack 3
    ng serve
  2. The log given by the failure. Normally this include a stack trace and some
    more information.
    Browser console error:
    Uncaught TypeError: uri.match is not a function
  3. Mention any other details that might be useful.

Thanks! We'll be in touch soon.

@terencewhitenz
Copy link

I had the same issue. I'll see if I can find the original source for this and link it in, but you can edit the file node_modules/@angular/compiler/src/metadata_resolver.js and change the following line

var scheme = url_resolver_1.getUrlScheme(moduleId);

to

var scheme = url_resolver_1.getUrlScheme(moduleId.toString());

until the fix comes through.

@RicardoVaranda
Copy link
Contributor Author

Fixed by removing moduleID from all components.

@terencewhitenz
Copy link

Original source #1665 (comment)

The problem with removing moduleID is that you can only really do it for your components, not for externals, and you may have to add your own back in when the fix is through.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants