Version 3.0.5 of awesome-typescript-loader just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As awesome-typescript-loader is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

ERROR in ./node_modules/angular2-focus/src/focus.module.ts
Module build failed: Error: C:\loltlv\node_modules\angular2-focus\src\focus.module.ts is missing from the TypeScript compilation. Please make sure it is in
your tsconfig via the 'files' or 'include' property.
The missing file seems to be part of a third party library. TS files in published libraries are often a sign of a badly packaged library. Please open an is
sue in the library repository to alert its author and ask them to package the library using the Angular Package Format (https://goo.gl/jB3GVv).
at AngularCompilerPlugin.getCompiledFile (C:\loltlv\node_modules@ngtools\webpack\src\angular_compiler_plugin.js:674:23)
at plugin.done.then (C:\loltlv\node_modules@ngtools\webpack\src\loader.js:467:39)
at process._tickCallback (internal/process/next_tick.js:109:7)
ERROR in ./node_modules/ng2-file-drop/index.ts
Module build failed: Error: C:\loltlv\node_modules\ng2-file-drop\index.ts is missing from the TypeScript compilation. Please make sure it is in your tsconf
ig via the 'files' or 'include' property.
The missing file seems to be part of a third party library. TS files in published libraries are often a sign of a badly packaged library. Please open an is
sue in the library repository to alert its author and ask them to package the library using the Angular Package Format (https://goo.gl/jB3GVv).
at AngularCompilerPlugin.getCompiledFile (C:\loltlv\node_modules@ngtools\webpack\src\angular_compiler_plugin.js:674:23)
at plugin.done.then (C:\loltlv\node_modules@ngtools\webpack\src\loader.js:467:39)
at process._tickCallback (internal/process/next_tick.js:109:7)

Version 2.4.1 of typescript just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As typescript is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Replaced the old Node.js version in your .nvmrc with the new one

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

I get the following error when running NG Build on Angular-CLI 1.5.0. I was converting over to Angular 5.0. When I removed module everything worked.

ERROR in TypeError: staticSymbol.assertNoMembers is not a function
at AotSummaryResolver.resolveSummary (C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@angular\compiler\bundles\compiler.umd.js:31928:22)
at CompileMetadataResolver._loadSummary (C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@angular\compiler\bundles\compiler.umd.js:14709:66)
at CompileMetadataResolver.isDirective (C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@angular\compiler\bundles\compiler.umd.js:15003:23)
at CompileMetadataResolver._getTypeDescriptor (C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@angular\compiler\bundles\compiler.umd.js:15269:18)
at C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@angular\compiler\bundles\compiler.umd.js:15131:78
at Array.forEach ()
at CompileMetadataResolver.getNgModuleMetadata (C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@angular\compiler\bundles\compiler.umd.js:15114:49)
at visitLazyRoute (C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@angular\compiler\bundles\compiler.umd.js:29937:104)
at AotCompiler.listLazyRoutes (C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@angular\compiler\bundles\compiler.umd.js:29905:20)
at AngularCompilerProgram.listLazyRoutes (C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@angular\compiler-cli\src\transformers\program.js:157:30)
at Function.NgTools_InternalApi_NG_2.listLazyRoutes (C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@angular\compiler-cli\src\ngtools_api.js:44:36)
at AngularCompilerPlugin._getLazyRoutesFromNgtools (C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@ngtools\webpack\src\angular_compiler_plugin.js:246:66)
at Promise.resolve.then.then (C:\Users\Gary\WebstormProjects\ConstituentManager2\node_modules@ngtools\webpack\src\angular_compiler_plugin.js:542:50)
at

Since the version has upgraded to version 4 upgrading the application to angular v4 might help the community

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

hello guys, Do you plan to update this library? to be compatible with angular 6

Describe the bug
I have a dynamic form in which controls are generated dynamically. Here is a sample control:
<mat-form-field class="form-field" [hintLabel]="formEditorModel.hint">
<mat-label>{{formEditorModel.label}}</mat-label>
<input matInput type="text" autocomplete="off" focus="{{formEditorModel.autoFocus}}" placeholder="{{formEditorModel.placeHolder}}" formControlName="{{formEditorModel.key}}" [required]="formEditorModel.required">
<button tabindex="-1" *ngIf="form.controls[formEditorModel.key].value" (click)="form.controls[formEditorModel.key].reset()" matSuffix mat-icon-button aria-label="Clear"> <mat-icon>close</mat-icon> </button>
<mat-error>{{GetFormError()}}</mat-error>
<mat-hint align="end">{{GetHint()}}</mat-hint>
</mat-form-field>

As you can see I have used the angular material here. I have a mat-form-field. Inside that there are usual components like Label, Input, Suffix clear button, Error text and Hint text.

Form has a submit button and a reset/cancel button. Submit button is the default action and works correctly. When the focus directive is not used and we enter data into the control and hit enter, the form is submitted. But when focus is used and we hit enter, the suffix clear button is clicked and the data entered in the control is cleared.

To Reproduce
Steps to reproduce the behavior:
Add the provided mat-form-field in a angular 6 material form.
Enter some data into the input control
Press Enter/return button

Entered text gets cleared.

Expected behavior
Not to focus on Any suffix button in mat-form-field when the focus is on the control. So that when we press enter it calls the default form action and not any unwanted things.

Screenshots

Desktop (please complete the following information):

• OS: windows 10 pro
• Browser Google Chrome
• Version 67

Version 4.2.2 of @angular/core just got published.

This version is covered by your current version range and after updating it in your project the build failed.

@angular/core is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Focus works perfectly fine when enabled at first, if i try to make focus false and then add true again nothing happens but ng-reflect seems to update the state from false to true but the element doesnt not get focused

To Reproduce
Steps to reproduce the behavior:

1. Make the focus property false initially
2. Make the property true, the element should be focused now
3. Make the property false
4. Now make it true again

Expected behavior
The element should be focused again

I can't give you example, because it is very specific. I used focus directive in the cell of infinity scroll table and it corrupted scroll. The same directive has same problem. Fortunately, there is good decision:

setTimeout(() => {
    this.giveFocus();
})

Use setTimeout! I made several components with focus (oi.select one of them) and I had same problems. In Angular, React, Vanilla etc. and I understood the main thing - newer use set focus without setTimeout. This is one of rare places where its use is justified

Version 0.9.37 of @types/core-js just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As @types/core-js is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 5.3.2 of rxjs just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As rxjs is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Hi @spirosikmd,

I used this module and config successful. Then user can't focus other elements! It really is wrong :3
I think that it just should focus the first time 👍

Regards,
Max

get Uncaught Error: Unexpected value '[object Object]' imported by the module 'AppModule'. Please add a @NgModule annotation.

indeed in my app.module.ts, I have
import { FocusModule } from 'angular2-focus';

imports....
FocusModule.forRoot()

Can you advise?

Version 14.2.0 of browserify just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As browserify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴