-
Notifications
You must be signed in to change notification settings - Fork 773
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
Source map path in npm release causing warnings #227
Comments
@mmalerba - I think we still need the |
@hansl Do you know why these are being generated with an absolute path? |
* Bumps all of the `@angular` dependencies to 4 and Material to 2.0.0-beta.3. * Fixes a few linter errors. * Fixes an issue that prevented AoT from working under Angular 4. * Moves away from a few of the APIs that were deprecated in Angular 4. * Fixes issues with the testing setup which prevented the module from compiling with Angular 4. * Fixes the demo app not working properly due to the Material theme not being included correctly. Fixes angular#254, angular#236, angular#227.
* Bumps all of the `@angular` dependencies to 4 and Material to 2.0.0-beta.3. * Fixes a few linter errors. * Fixes an issue that prevented AoT from working under Angular 4. * Moves away from a few of the APIs that were deprecated in Angular 4. * Fixes issues with the testing setup which prevented the module from compiling with Angular 4. * Fixes the demo app not working properly due to the Material theme not being included correctly. Fixes angular#254, angular#236, angular#227.
Closing as not valid with Angular 4.1.x and beta.8 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
For 2.0.0-rc.1, the official package pulled down from npm has most of the compiled JavaScript files ending with a terminating
#sourceMappingURL
element bearing what appears to be a path to one of the author's folders. Namely,/usr/local/google/home/mmalerba/flex-layout/src/lib...
. This causes most of my tooling (including webpack if an angular-cli project using this flex-layout is later ejected) to throw off a ton of warnings because the sourcemap url is invalid. These warnings also collect in Chrome's developer panel as well when Chrome attempts to load symbols from the sourcemaps.Based upon other npm packages, it would seem the pathing shouldn't be included in the distribution so that the associated sourcemap provided in the package can be loaded.
The text was updated successfully, but these errors were encountered: