vsfedorenko / ngx-fullpage

Angular 2 fullPage.js port library

ngx-fullpage

Create Beautiful Fullscreen Scrolling websites (now with Angular 2 and above)!

This is an Angular fullPage.js port library.

New:

• Project is updated to support Angular 7 !

Help wanted

As for now, I have no enough time to work on the this library. I am a backend developer, write Java / Python programs and that's the reason why library updates are so rare. I am not able to follow all the new trends in Angular, fullpage.js and frontend in general.

I am looking for collaborators who could help me to keep library up to date and resolve incoming PR's and issues. If you are interested in it, contact me via email: [email protected]

Demo

Check out the live demo HERE

Docs

For docs checkout our WIKI

For typedocs checkout this LINK

ngx-fullpage's Issues

Fullpage.js can only be initialized once and you are doing it multiple times!

This happens with simple back and forth of the routes using the browser navigation.

For example, steps:

• go to homapge of your app, say /home
• click to go to fullpage.js enabled component, say /withfullpage
• click your browser back button, should go to /home
• then click forward which should go to /withfullpage

The error is: fullPage: Fullpage.js can only be initialized once and you are doing it multiple times! and the page is broken with regards to it being fullpage enabled.

An in-range update of core-js is breaking the build 🚨

Version 2.5.0 of core-js just got published.

Branch	Build failing 🚨
Dependency	core-js
Current Version	2.4.1
Type	devDependency

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

As 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 99 commits.

• 63ae52d 2.5.0
• 998f32e update eslint
• 9025b48 add .of and .from methods on collection constructors to readme
• 20f055b add Array#flatten and Array#flatMap to readme
• 860efb6 fix a typo
• b9203ee update list of iterable DOM collections in readme
• b4c2e5e remove some unused variables, update changelog
• fc32be8 add Promise#try to readme
• ea82fd9 remove caching Function#name, fix #296
• fd850c3 add Promise#finally to readme
• a41dd09 fix IE11 WeakMap frozen keys after zloirock/core-js@a69f577
• 09f45b6 remove tests of excess DOM collections methods - FF have it, I don't think that removing those methods in core-js make sense
• d230280 fix the list of whitespaces in the Number constructor test
• 7c39430 move Array#flatten and Array#flatMap to stage 1 per July TC39 meeting
• d35736f move Promise#finally to stage 3 per July TC39 meeting

There are 99 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of zone.js is breaking the build 🚨

Version 0.8.12 of zone.js just got published.

Branch	Build failing 🚨
Dependency	zone.js
Current Version	0.8.11
Type	devDependency

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

As zone.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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 7 commits.

• 3511159 chore: release v0.8.12
• 68aa03e fix(toString): fix #802, fix ios 9 MutationObserver toString error (#803)
• 7bd1418 fix(xhr): inner onreadystatechange should not triigger Zone callback (#800)
• 857929d feat(patch): fix #758, patch cordova.exec success/error with zone.wrap (#789)
• 7ca3995 feat(patch): fix #696, patch HTMLCanvasElement.toBlob as MacroTask (#788)
• 67634ae fix(patch): fix #791, fix mediaQuery/Notification patch use wrong global (#792)
• 0c5da04 fix(doc): fix #793, fix confuse bluebird patch doc (#794)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

It does not work with angular-universal

documentation for destroy option

I see the full page.destroy() option in MnFullpageService. But I am not sure how to invoke that. If possible it would be great to learn how to do this and have it in the documentation.

An in-range update of ts-node is breaking the build 🚨

Version 3.0.5 of ts-node just got published.

Branch	Build failing 🚨
Dependency	ts-node
Current Version	3.0.4
Type	devDependency

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

As ts-node 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 7 commits.

• c18331a 3.0.5
• 5cf97b1 Add --inspect-brk to known flags (#343)
• 7dfb3e3 Pin node tests at 6.x (#340)
• 633d537 chore(package): update chai to version 4.0.1 (#337)
• b751a56 Define exports and improve getTypeInfo help (#332)
• d018300 Update yn default option
• cc3bf22 Expose _ bin file for consumers to use

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @angular/compiler-cli is breaking the build 🚨

Version 4.1.0 of @angular/compiler-cli just got published.

Branch	Build failing 🚨
Dependency	@angular/compiler-cli
Current Version	4.0.3
Type	devDependency

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

As @angular/compiler-cli 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 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/meiblorn/ngx-fullpage/builds/226086022)

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of rxjs is breaking the build 🚨

Version 5.4.1 of rxjs just got published.

Branch	Build failing 🚨
Dependency	rxjs
Current Version	5.4.0
Type	devDependency

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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

AOT compliant support

Hello,

I love your library, however with aot build, I get the following error :

ERROR in Unexpected value 'MnFullpageDirective in node_modules/ng2-fullpage/components/fullpage/mnFullpage.directive.d.ts' imported by the module 'HomepageModule in src/app/homepage/homepage.module.ts'

It seems that your project is missing the .metadata.json file (angular/angular#11262)

An in-range update of npm-check-updates is breaking the build 🚨

Version 2.11.3 of npm-check-updates just got published.

Branch	Build failing 🚨
Dependency	npm-check-updates
Current Version	2.11.2
Type	devDependency

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

As npm-check-updates 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 2 commits.

• ddbc457 2.11.3
• 88d1ec0 update require-dir, which fix node v8.0.0

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Doesn't working on angular-cli latest version above 1.0.3

Displayed error on console.

compiler.es5.js:1540Uncaught Error: Unexpected value 'MnFullpageDirective' declared by the module 'AppModule'. Please add a @Pipe/@Directive/@Component annotation.(…)

An in-range update of @angular/core is breaking the build 🚨

Version 4.2.3 of @angular/core just got published.

Branch	Build failing 🚨
Dependency	@angular/core
Current Version	4.2.2
Type	devDependency

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

As @angular/core 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

fullpage only works with ngFor if adding an irrelevant div as first section

I seem to be forced to add a fake section to activate the rest of the ngFor loop with ngx-fullpage (see line "Why do I need this"). I don't understand why, I've tried removing specific classes, but nothing seems to help.

<div mnFullpage [mnFullpageNavigation]="true" [mnFullpageSlidesNavPosition]="false">

    <div id="section0" class="section fp-section fp-table"></div> <!-- Why do I need this??-->

    <div [attr.id]="'section' + i " class="section fp-section fp-table"
             *ngFor="let item of items; let i = index">
            <h2> {{item.name}}</h2>
           <span>
            <img
             [src]="item.imagePath"
             alt="{{item.name}}"
             class="img-responsive">
           </span>
         </div>
    </div>
  </div>

An in-range update of @types/node is breaking the build 🚨

Version 7.0.24 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.23
Type	devDependency

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

As @types/node 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Unexpected value 'MnFullpageDirective' declared by the module 'AppModule'. Please add a @Pipe/@Directive/@Component annotation

Followed the first example given at https://www.npmjs.com/package/ng2-fullpage

The only difference is that because I only just installed angular2 so my package.json file has V4

"dependencies": {
    "@angular/animations": "^4.2.2",
    "@angular/common": "^4.2.2",
    "@angular/compiler": "^4.2.2",
    "@angular/core": "^4.2.2",
    "@angular/forms": "^4.2.2",
    "@angular/http": "^4.2.2",
    "@angular/platform-browser": "^4.2.2",
    "@angular/platform-browser-dynamic": "^4.2.2",
    "@angular/router": "^4.2.2",
    "core-js": "^2.4.1",
    "ng2-fullpage": "^2.1.0",
    "rxjs": "^5.4.0",
    "zone.js": "^0.8.12"
  },

The default project compiles OK and shows the home page - as expected

When I put in the additional lines as recommend on your NPM page then the code also compiles OK and webpack starts, but at runtime - I'm getting this console error ....

and only the default "Loading ..." renders

compiler.es5.js:1917 Uncaught Error: Unexpected value 'MnFullpageDirective' declared by the module 'AppModule'. Please add a @Pipe/@Directive/@Component annotation.
    at syntaxError (webpack:///../~/@angular/compiler/@angular/compiler.es5.js?:1917:34)
    at eval (webpack:///../~/@angular/compiler/@angular/compiler.es5.js?:15649:40)
    at Array.forEach (native)
    at CompileMetadataResolver.getNgModuleMetadata (webpack:///../~/@angular/compiler/@angular/compiler.es5.js?:15631:54)
    at JitCompiler._loadModules (webpack:///../~/@angular/compiler/@angular/compiler.es5.js?:26908:70)
    at JitCompiler._compileModuleAndComponents (webpack:///../~/@angular/compiler/@angular/compiler.es5.js?:26881:36)
    at JitCompiler.compileModuleAsync (webpack:///../~/@angular/compiler/@angular/compiler.es5.js?:26810:37)
    at PlatformRef_._bootstrapModuleWithZone (webpack:///../~/@angular/core/@angular/core.es5.js?:4799:25)
    at PlatformRef_.bootstrapModule (webpack:///../~/@angular/core/@angular/core.es5.js?:4785:21)
    at Object.eval (webpack:///./main.ts?:10:53)
    at eval (webpack:///./main.ts?:12:30)
    at Object.298 (http://localhost:3000/app.js:510:1)
    at __webpack_require__ (http://localhost:3000/polyfill.js:55:30)
    at eval (webpack:///multi_../~/webpack-dev-server/client?:2:18)
    at Object.807 (http://localhost:3000/app.js:833:1)
    at __webpack_require__ (http://localhost:3000/polyfill.js:55:30)
    at webpackJsonpCallback (http://localhost:3000/polyfill.js:26:23)
    at http://localhost:3000/app.js:1:1

TypeError: $(...).fullpage is not a function - in angular 4 (angular cli)

:3000/node_modules/@angular/core/bundles/core.umd.js:1091 ERROR Error: Uncaught (in promise): TypeError: $(...).fullpage is not a function
TypeError: $(...).fullpage is not a function

An in-range update of typedoc is breaking the build 🚨

Version 0.7.2 of typedoc just got published.

Branch	Build failing 🚨
Dependency	typedoc
Current Version	0.7.1
Type	devDependency

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

As typedoc 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

Check for `symbol.declarations`

Fixed

• Check for symbol.declarations before crashing

Commits

The new version differs by 7 commits.

• 22be6b6 0.7.2
• 5eb104b Tidy up symbol.declarations check
• be929bb Check for symbol.declarations (#518)
• 81779eb Check if the decorators are undefined in the export (#562)
• 6edcbd5 Updated import export whitespace for tslint (#558)
• 827effa fix(package): update typescript to version 2.3.4 (#519)
• 47a8b3d fix(package): update typescript to version 2.3.3 (#512)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Multiple initializations when used in multiple components

Hey there,

first of all, thanks a lot for developing this project!
I have tried to integrate the mnFullpage directive with an application that uses it in multiple components. When navigating between those components, the second time the directive is encountered (and on all subsequent encounters), fullPage.js throws the following error message and functionality breaks:

fullPage: Fullpage.js can only be initialized once and you are doing it multiple times!

I have created a PR that fixes this by destroying fullpage every time before initializing it. If you could accept the PR or offer any other kind of help/workaround for this issue in case I'm missing something, I would appreciate it a lot :)

Tons of warnings

Webpack output and chrome console generates such warnings

 ./~/ngx-fullpage/ngx-fullpage.js
Cannot find source file '../sources/ngx-fullpage.ts': Error: Can't resolve '../sources/ngx-fullpage.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage'
 @ ./src/app/app.module.ts 14:0-48
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/index.js
Cannot find source file '../../sources/components/index.ts': Error: Can't resolve '../../sources/components/index.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components'
 @ ./~/ngx-fullpage/ngx-fullpage.js 10:9-38
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/fullpage/index.js
Cannot find source file '../../../sources/components/fullpage/index.ts': Error: Can't resolve '../../../sources/components/fullpage/index.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components\fullpage'
 @ ./~/ngx-fullpage/components/index.js 6:14-41 7:14-41
 @ ./~/ngx-fullpage/ngx-fullpage.js
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/fullpage/mnFullpage.module.js
Cannot find source file '../../../sources/components/fullpage/mnFullpage.module.ts': Error: Can't resolve '../../../sources/components/fullpage/mnFullpage.module.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components\fullpage'
 @ ./~/ngx-fullpage/components/fullpage/index.js 6:26-56
 @ ./~/ngx-fullpage/components/index.js
 @ ./~/ngx-fullpage/ngx-fullpage.js
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/fullpage/mnFullpage.directive.js
Cannot find source file '../../../sources/components/fullpage/mnFullpage.directive.ts': Error: Can't resolve '../../../sources/components/fullpage/mnFullpage.directive.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components\fullpage'
 @ ./~/ngx-fullpage/components/fullpage/index.js 8:29-62
 @ ./~/ngx-fullpage/components/index.js
 @ ./~/ngx-fullpage/ngx-fullpage.js
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/fullpage/mnFullpage-options.class.js
Cannot find source file '../../../sources/components/fullpage/mnFullpage-options.class.ts': Error: Can't resolve '../../../sources/components/fullpage/mnFullpage-options.class.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components\fullpage'
 @ ./~/ngx-fullpage/components/fullpage/index.js 10:33-70
 @ ./~/ngx-fullpage/components/index.js
 @ ./~/ngx-fullpage/ngx-fullpage.js
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/fullpage/mnFullpage.service.js
Cannot find source file '../../../sources/components/fullpage/mnFullpage.service.ts': Error: Can't resolve '../../../sources/components/fullpage/mnFullpage.service.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components\fullpage'
 @ ./~/ngx-fullpage/components/fullpage/index.js 12:27-58
 @ ./~/ngx-fullpage/components/index.js
 @ ./~/ngx-fullpage/ngx-fullpage.js
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

An in-range update of jasmine-spec-reporter is breaking the build 🚨

Version 4.1.1 of jasmine-spec-reporter just got published.

Branch	Build failing 🚨
Dependency	jasmine-spec-reporter
Current Version	4.1.0
Type	devDependency

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

As jasmine-spec-reporter 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v4.1.1

Bugfix

• Correct report from jasmineStarted event #185

Commits

The new version differs by 59 commits.

• 9ec77f2 4.1.1
• 8a90ee1 Update CHANGELOG.md
• c50e436 chore(yarn.lock): update yarn.lock
• 04381ca chore(package): update @types/node to version 8.0.1
• 65756ff chore(yarn.lock): update yarn.lock
• 3083f9f chore(package): update @types/node to version 8.0.0
• e790753 Update screenshot & Readme
• 8ce5fee chore(yarn.lock): update yarn.lock
• 7c1f5f1 chore(package): update jasmine-core to version 2.6.4
• 0b8ce98 Correct report from jasmineStarted event
• 3d18c0b chore(yarn.lock): update yarn.lock
• e3ed25e chore(package): update jasmine-core to version 2.6.3
• 0f0ac6f chore(yarn.lock): update yarn.lock
• d6bb126 chore(package): update @types/node to version 7.0.29
• 2ff30bc chore(yarn.lock): update yarn.lock

There are 59 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of karma is breaking the build 🚨

Version 1.7.1 of karma just got published.

Branch	Build failing 🚨
Dependency	karma
Current Version	1.7.0
Type	devDependency

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

As karma 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 3 commits.

• ee40570 chore: release v1.7.1
• 66b08e6 chore: update contributors
• ea32194 feat(deps): add support for node@8

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @angular/compiler-cli is breaking the build 🚨

Version 4.2.3 of @angular/compiler-cli just got published.

Branch	Build failing 🚨
Dependency	@angular/compiler-cli
Current Version	4.2.2
Type	devDependency

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

As @angular/compiler-cli 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Dynamic section count with *ngFor not refreshing

I am also having the problem of implementing *ngFor similar to this issue:
#180
In this issue a modification of the sources are suggested.

But what if the count of sections is changed dynamically during the page visit? For me the amount of section depends on which category is selected in a sidebar. Therefore the an "currentProject" object is bind in the for loop like this
<div *ngFor="let img of currentProject.images" class="section">

So even if I get ngx-fullpage working with the workaround described in the other issue, I will not have it updated every time the currentProject object and therefore the amount of images changes, because ngx-fullpage would only be initialized once after the ngviewinit.

I also tried to destroy('all') and then initialize again when the project was chosen, but so far it did not succeed. But maybe the view wasn't updated fast enough before I reinitialized it.

Has somebody encounterd a smiliar problem and can help me with that?

An in-range update of @types/jquery is breaking the build 🚨

Version 2.0.46 of @types/jquery just got published.

Branch	Build failing 🚨
Dependency	@types/jquery
Current Version	2.0.45
Type	devDependency

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

As @types/jquery 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Click events trigger "Cannot read property 'moveSectionDown' of undefined" error

Thank you for making this directive. It's been very helpful so far, I'm just having this single issue.

When I attempt to add buttons and/or click events to trigger it to move down, or up, to the next section, I receive the following error.

I'm using Angular 4.4.3, and attempting to use the buttons straight from the demo.

<button (click)="fullpageService.moveSectionUp();">Move section up</button>

I'm importing import { MnFullpageModule } from 'ngx-fullpage'; at the top of my app.module.ts and importing MnFullpageModule.forRoot() into @NgModule lower down in app.module.ts.

This is all I could find, in the documentation.

I cant get callbacks to work

Im a bit confused about the use of callbacks in ngx-fullpage. Is there any example on how to get it done?

An in-range update of @angular/router is breaking the build 🚨

Version 4.2.3 of @angular/router just got published.

Branch	Build failing 🚨
Dependency	@angular/router
Current Version	4.2.2
Type	devDependency

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

As @angular/router 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

scrollOverflow not working

Hello @meiblorn, thanks for making this a ng directive.
I'm having some issues with the plugin, I'm setting scrolloverflow to true in my app.component.ts like:

@Output() public options: MnFullpageOptions = new MnFullpageOptions({
        slidesNavigation: true,
        navigation: true,
        keyboardScrolling: true,
        controlArrows: true,
        css3: true,
        scrollOverflow: true
      });

Also on my angular-cli.json I got this

"scripts": [
        "../node_modules/jquery/dist/jquery.js",
        "../node_modules/fullpage.js/vendors/jquery.slimscroll.min.js",
        "../node_modules/fullpage.js/vendors/scrolloverflow.js",
        "../node_modules/fullpage.js/dist/jquery.fullpage.js"
],

And I'm seeing this error on my console:

I think I have everything that's needed for it to work, what am I missing?

Thanks!

UPDATE

You can see the repo here, https://github.com/angelitaooo/angular-fullpage-slider-poc

Thanks!

Hola meiblorn, question about callback function.

Is callback function is ported from fullpage.js?

Unable to install NPM dependency

└─┬ [email protected] 
  ├── [email protected] 
  ├── UNMET PEER DEPENDENCY [email protected]
  └── UNMET PEER DEPENDENCY zone.js@^0.6.21

npm WARN @angular/[email protected] requires a peer of [email protected] but none was installed.
npm WARN @angular/[email protected] requires a peer of zone.js@^0.6.21 but none was installed.

on macOS Sierra

An in-range update of @angular/common is breaking the build 🚨

Version 4.2.3 of @angular/common just got published.

Branch	Build failing 🚨
Dependency	@angular/common
Current Version	4.2.2
Type	devDependency

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

As @angular/common 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Problems with ASP.NET Core / Angular 4 stack (possible due to AppState error)

I have created an Angular 4 / ASP.NET Core application using VS2017's built-in example application. I wanted to add fullpage.js support using your directive and followed the webpack installation guide. Alas, the result is just my divs displayed like they would display without fullpage.js, i.e. one after another without any fullpage-mechanics.

The instructions were followed correctly, except for the "AppState" removed, because TS could not detect what it is. Server pre-rendering has been disabled, and there are no errors anywhere. Is there any way to fix this or should I try to implement fullpage.js without this directive?

Unexpected value 'MnFullpageDirective' declared by the module 'AppModule'

Just trying to add your code, as written in docs.
After adding to declarations, although webpack compiles the code, the following error appears in the console:

compiler.umd.js?9df7:14374Uncaught Error: Unexpected value 'MnFullpageDirective' declared by the module 'AppModule'
at eval (eval at (http://localhost:8080/vendor.js:94:2), :14374:33)
at Array.forEach (native)
at CompileMetadataResolver.getNgModuleMetadata (eval at (http://localhost:8080/vendor.js:94:2), :14361:51)
at RuntimeCompiler._compileComponents (eval at (http://localhost:8080/vendor.js:94:2), :17063:49)
at RuntimeCompiler.compileModuleAndComponents (eval at (http://localhost:8080/vendor.js:94:2), :17001:39)
at RuntimeCompiler.compileModuleAsync (eval at (http://localhost:8080/vendor.js:94:2), :16992:23)
at PlatformRef.bootstrapModuleWithZone (eval at (http://localhost:8080/vendor.js:100:2), :6684:29)
at PlatformRef.bootstrapModule (eval at (http://localhost:8080/vendor.js:100:2), :6666:25)
at Object.eval (eval at (http://localhost:8080/app.js:87:2), :9:53)
at eval (eval at (http://localhost:8080/app.js:87:2), :11:30)
at Object. (http://localhost:8080/app.js:87:2)
at webpack_require (http://localhost:8080/polyfills.js:51:30)
at Object. (http://localhost:8080/app.js:6:19)
at webpack_require (http://localhost:8080/polyfills.js:51:30)
at webpackJsonpCallback (http://localhost:8080/polyfills.js:22:20)
at http://localhost:8080/app.js:1:1

An in-range update of @angular/platform-browser-dynamic is breaking the build 🚨

Version 4.2.3 of @angular/platform-browser-dynamic just got published.

Branch	Build failing 🚨
Dependency	@angular/platform-browser-dynamic
Current Version	4.2.2
Type	devDependency

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

As @angular/platform-browser-dynamic 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of jasmine-core is breaking the build 🚨

Version 2.6.3 of jasmine-core just got published.

Branch	Build failing 🚨
Dependency	jasmine-core
Current Version	2.6.2
Type	devDependency

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

As jasmine-core 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

2.6.3

Please see the release notes

Commits

The new version differs by 2 commits.

• ca5b1de bump version to 2.6.3
• a3bc747 Make sure the queue runner goes async for async specs

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @angular/core is breaking the build 🚨

Version 4.1.1 of @angular/core just got published.

Branch	Build failing 🚨
Dependency	@angular/core
Current Version	4.1.0
Type	devDependency

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

As @angular/core 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Demo doesen't work?

C:\Users\user\scl\scl>ng serve --aot

....

ERROR in Error: Unexpected value 'MnFullpageDirective in C:/Users/user/scl/scl/node_modules/ng2-fullpage/components/fullpage/mnFullpage.directive.d.ts' declared by the module 'AppModule in C:/Users/user/scl/scl/src/app/app.module.ts'. Please add a @Pipe/@Directive/@component annotation.

`import { NgModule } from "@angular/core";
import { BrowserModule } from "@angular/platform-browser";

import { AppComponent } from "./app.component";
import { MnFullpageDirective, MnFullpageService } from "ng2-fullpage";

@NgModule({
bootstrap: [ AppComponent ],
declarations: [
AppComponent,
MnFullpageDirective // add MnFullpageDirective declaration here
],
imports: [
BrowserModule,
],
providers: [
MnFullpageService // also add MnFullpageService provider here
]
})
export class AppModule {

}`

Followed this: https://www.npmjs.com/package/ng2-fullpage
Did I do anything wrong or is this not working ?

Lazy Load Module multiple initializations

Hello,
i'm using mnFullPage in a lazy loaded module and it works at the beggining, but when i switch back to this route i got this error 'fullPage: Fullpage.js can only be initialized once and you are doing it multiple times!'

I tried to destroy it OnDestroy event with no success

edit:
It worked with the "all" option at destroy method, but i don't think that this is the proper way to get it work
this.mnFullpageService.destroy('all');

An in-range update of tslint is breaking the build 🚨

Version 5.4.3 of tslint just got published.

Branch	Build failing 🚨
Dependency	tslint
Current Version	5.4.2
Type	devDependency

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

As tslint 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v5.4.3

🛠 Bugfixes

• [bugfix] Fixed regression with empty --out file (#2867)
• [bugfix] unified-signatures: Don't suggest to unify rest parameters. (#2874)
• [bugfix] binary-expression-operand-order: Allow if both sides of the binary expression are literals. (#2873)
• [bugfix] Restore compatibility with [email protected] and 2.2 for whitespace, space-before-function-paren and deprecation (#2893)
• [docs] no-string-literal: Fix documentation (#2875)

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of sort-package-json is breaking the build 🚨

Version 1.7.0 of sort-package-json just got published.

Branch	Build failing 🚨
Dependency	sort-package-json
Current Version	1.6.1
Type	devDependency

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

As sort-package-json 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 1 commits.

• 1688c95 feat: add module, which is the new jsnext:main (#16)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @angular/compiler is breaking the build 🚨

Version 4.2.3 of @angular/compiler just got published.

Branch	Build failing 🚨
Dependency	@angular/compiler
Current Version	4.2.2
Type	devDependency

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

As @angular/compiler 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

mnFullpage options not being applied to ngFor iterations

Hi @meiblorn

If I use an ngFor loop and wrap it around the sections, the mnFullpage options aren't being applied.

Any remedy for this? I think it would be a good feature for large reports etc.

browser_adapter.js:84 EXCEPTION: TypeError: Cannot read property 'top' of undefined

When navigating through slides

Docs: add note for view encapsulation

Hello!
It took me about 2 hours to figure out why ng2-fullpage isn't working with my project, Then finally i changed my view encapsulation from native to none and now it is working perfectly.
Please add a note in docs about angular 2 view encapsulation that it has to be set to none before setting ng2-fullpage. :)

zone.js:101 GET http://localhost:3000/ng2-fullpage 404 (Not Found)

I started an Angular 2 app using the 5 Minute Quickstart which uses SystemJS instead of WebPack.

Then I added in ng2-fullpage.

When I startup and navigate to the site I am getting this error:
zone.js:101 GET http://localhost:3000/ng2-fullpage 404 (Not Found)

package.json

{
  "name": "angular2-quickstart",
  "version": "1.0.0",
  "scripts": {
    "start": "tsc && concurrently \"npm run tsc:w\" \"npm run lite\" ",
    "lite": "lite-server",
    "postinstall": "typings install",
    "tsc": "tsc",
    "tsc:w": "tsc -w",
    "typings": "typings"
  },
  "license": "ISC",
  "dependencies": {
    "@angular/common": "2.0.0-rc.1",
    "@angular/compiler": "2.0.0-rc.1",
    "@angular/core": "2.0.0-rc.1",
    "@angular/http": "2.0.0-rc.1",
    "@angular/platform-browser": "2.0.0-rc.1",
    "@angular/platform-browser-dynamic": "2.0.0-rc.1",
    "@angular/router": "2.0.0-rc.1",
    "@angular/router-deprecated": "2.0.0-rc.1",
    "@angular/upgrade": "2.0.0-rc.1",
    "angular2-in-memory-web-api": "0.0.7",
    "bootstrap": "^3.3.6",
    "es6-shim": "^0.35.0",
    "jquery": "2.2.4",
    "ng2-fullpage": "^1.2.1",
    "reflect-metadata": "^0.1.3",
    "rxjs": "5.0.0-beta.6",
    "systemjs": "0.19.27",
    "zone.js": "^0.6.12"
  },
  "devDependencies": {
    "concurrently": "^2.0.0",
    "lite-server": "^2.2.0",
    "typescript": "^1.8.10",
    "typings": "^0.8.1"
  }
}

app.components.ts

import { Component } from '@angular/core';
import {FullpageDirective} from 'ng2-fullpage';


@Component({
    selector: 'my-app',
    directives: [FullpageDirective],
    template:  `
        <div >
            <div class="section"> Some section 1 </div>
                <div class="section"> Some section 2 </div>
                <div class="section">
                    <div class="slide"> Slide 1 </div>
                    <div class="slide"> Slide 2 </div>
                    <div class="slide"> Slide 3 </div>
                    <div class="slide"> Slide 4 </div>
                </div>
            <div class="section"> Some section 4 </div>
        </div>
    `
})
export class AppComponent { }

Any ideas on what is wrong?

Thank you for porting this to Angular 2!

An in-range update of @types/node is breaking the build 🚨

Version 7.0.17 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.16
Type	devDependency

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

As @types/node 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

how to use with the new typings tool

cesco@cesco-desktop: ~/code/src/bitbucket.org/cescoferraro/cesco on master [!?]
$ typings search --name=jquery 
Viewing 1 of 1

NAME   SOURCE HOMEPAGE           DESCRIPTION VERSIONS UPDATED                 
jquery dt     http://jquery.com/             1        2016-04-17T21:32:36.000Z
cesco@cesco-desktop: ~/code/src/bitbucket.org/cescoferraro/cesco on master [!?]
$ typings install jquery --save --ambient
typings ERR! message Unable to find "jquery" ("npm") in the registry. Did you want to try searching another source? Also, if you want contribute these typings, please help us: https://github.com/typings/registry
typings ERR! caused by https://api.typings.org/entries/npm/jquery/versions/latest responded with 404, expected it to equal 200

typings ERR! cwd /home/cesco/code/src/bitbucket.org/cescoferraro/cesco
typings ERR! system Linux 3.19.0-32-generic
typings ERR! command "/usr/bin/nodejs" "/usr/bin/typings" "install" "jquery" "--save" "--ambient"
typings ERR! node -v v5.11.0
typings ERR! typings -v 1.0.4

typings ERR! If you need help, you may report this error at:
typings ERR!   <https://github.com/typings/typings/issues>

An in-range update of @angular/platform-browser is breaking the build 🚨

Version 4.2.3 of @angular/platform-browser just got published.

Branch	Build failing 🚨
Dependency	@angular/platform-browser
Current Version	4.2.2
Type	devDependency

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

As @angular/platform-browser 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of karma-chrome-launcher is breaking the build 🚨

Version 2.1.1 of karma-chrome-launcher just got published.

Branch	Build failing 🚨
Dependency	karma-chrome-launcher
Current Version	2.1.0
Type	devDependency

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

As karma-chrome-launcher 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

v2.1.1

Bug Fixes

• add disable-renderer-backgrounding flag (6bfc170), closes #123

Commits

The new version differs by 6 commits0.

• f61d786 chore: release v2.1.1
• 253f168 chore: update contributors
• 0db9489 Merge pull request #124 from cexbrayat/feat/disable-renderer-backgrounding
• 6bfc170 fix: add disable-renderer-backgrounding flag
• 5b5b4ae Merge pull request #121 from karma-runner/add-supported-browsers-info
• aa5b581 docs: add supported browsers list

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Problem when run npm run build