Code Monkey home page Code Monkey logo

angularjs-typescript-webpack's Introduction

angularjs-typescript-webpack starter

Greenkeeper badge

This project is an application skeleton for AngularJS 1.7, typescript 2.9 and webpack 4.5

Project uses angular-ts-decorators to mimic angular 2+ style development in angularjs environment with typescript and webpack.

Getting Started

To get you started you can simply clone the angularjs-typescript-webpack repository.

Some of the project dependencies are used just for example and can be removed if not needed.

Clone angularjs-typescript-webpack

Clone the angularjs-typescript-webpack repository using git:

Install Dependencies

We have two kinds of dependencies in this project: development tools and application specific packages. They are both managed with npm in package.json as devDependencies and dependencies respectively.

npm install

Directory Layout

src/                    --> all of the source files for the application
  assets/           --> static app assets
  components/           --> all app specific modules
  services/                --> all app common services
  main.ts                --> main application module
  index.html            --> app layout file (the main html template file of the app)

Running the App during Development

The angularjs-typescript-webpack project comes preconfigured with a local development webserver. It is a webpack-dev-server, that supports hot reload. You can start this webserver with npm start.

Now browse to the app at http://localhost:3000/.

Building and running the App in Production

To build the application for production just run npm build, it creates dist directory that have the production optimized build.

angularjs-typescript-webpack's People

Contributors

greenkeeper[bot] avatar vsternbach avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

angularjs-typescript-webpack's Issues

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

The devDependency @types/node was updated from 10.11.0 to 10.11.1.

🚨 View failing branch.

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

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

ENHANCEMENT: NgRedux

Perhaps introduce ngRedux/Thunk?

I personally like a more 'ducks' approach, where the reducers house the action/store/reducer logic in one reducer file.

If you would like I can try and do a PR later next week?

gapi is not defined

I am getting an error 'gapi is not defined'

tasks.service.ts:82 ReferenceError: gapi is not defined
at TasksService.get [as gTasksAPI] (tasks.service.ts:189)
at TasksService.eval (tasks.service.ts:76)
at step (tasks.service.ts:49)
at Object.eval [as next] (tasks.service.ts:30)
at eval (tasks.service.ts:24)
at new $Q (angular.js:17348)
at __awaiter (tasks.service.ts:20)
at TasksService.getTasklists (tasks.service.ts:70)
at TasksListsComponent.eval (tasklists.component.ts:69)
at step (tasklists.component.ts:41)

tried installing npm install --save @types/gapi but no luck..

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

The dependency angular-ts-decorators was updated from 3.7.7 to 3.7.8.

🚨 View failing branch.

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

angular-ts-decorators is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

The devDependency @types/jquery was updated from 3.3.28 to 3.3.29.

🚨 View failing branch.

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

@types/jquery is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

The devDependency karma was updated from 4.1.0 to 4.2.0.

🚨 View failing branch.

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

karma is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v4.2.0

Bug Fixes

  • logging: Util inspect for logging the config. (#3332) (70b72a9)
  • reporter: format stack with 1-based column (#3325) (182c04d), closes #3324
  • server: Add error handler for webserver socket. (#3300) (fe9a1dd)
Commits

The new version differs by 13 commits.

  • 42933c9 chore: release v4.2.0
  • db1ea57 chore: update contributors
  • a1049c6 chore: update eslint packages to latest and fix complaints (#3312)
  • 70b72a9 fix(logging): Util inspect for logging the config. (#3332)
  • 1087926 fix typo: (#3334)
  • 182c04d fix(reporter): format stack with 1-based column (#3325)
  • f0c4677 docs(travis): Correct the docs to also show how to do it on Xenial (#3316)
  • 3aea7ec chore(deps): update core-js -> ^3.1.3 (#3321)
  • 5e11340 chore: revert back to Mocha 4 (#3313)
  • 1205bce chore(test): fix flaky test cases (#3314)
  • 7f40349 Cleanup dependencies (#3309)
  • 7828bea chore: update braces and chokidar to latest versions (#3307)
  • fe9a1dd fix(server): Add error handler for webserver socket. (#3300)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of fork-ts-checker-webpack-plugin is breaking the build 🚨

The devDependency fork-ts-checker-webpack-plugin was updated from 1.3.3 to 1.3.4.

🚨 View failing branch.

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

fork-ts-checker-webpack-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v1.3.4

1.3.4 (2019-05-22)

Bug Fixes

  • emit global errors even when checkSyntacticErrors: false (b2bda8f), closes #289
Commits

The new version differs by 19 commits.

  • c06ca75 test: should find global errors (checkSyntacticErrors: false)
  • b2bda8f fix: emit global errors even when checkSyntacticErrors: false
  • a3b723a refactor: move @types dependencies to devDependencies
  • a371944 refactor: πŸ’‘ convert last integration tests to typescript
  • 45f4a97 refactor: πŸ’‘ rename variables, add comments
  • 5fb3805 refactor: add tslint for integration tests
  • 3d220dd refactor: move fixtures out of integration folder
  • f0aa083 refactor: πŸ’‘ vue integration tests to typescript
  • 6915de9 don't fail if vue-loader/lib/plugin is not present
  • 6e99f75 refactor: πŸ’‘ split up test suite
  • 0f435ea refactor: πŸ’‘ remaining integration tests, split helpers up
  • 04d6bd1 change from ts-jest to jest with @babel/preset-typescript
  • 93da097 refactor: πŸ’‘ helpers to typescript, use in integration/index
  • 50112fb reduce diff
  • 61cb1a9 chore: πŸ”§ refactor integration tests for jest

There are 19 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

The devDependency @types/node was updated from 12.0.2 to 12.0.3.

🚨 View failing branch.

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

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Selector as undefined

I cloned this repo. The routing is not happening for "view1" or "view2". On debugging the selector is coming as 'undefined'

image

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

The devDependency node-sass was updated from 4.12.0 to 4.13.0.

🚨 View failing branch.

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

node-sass is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v4.13.0

Features

Community

Dependencies

Supported Environments

OS Architecture Node
Windows x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
OSX x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
Linux* x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**^, 12**^, 13**^
Alpine Linux x64 6, 8, 10, 11, 12, 13
FreeBSD i386 amd64 6, 8, 10, 12, 13

*Linux support refers to Ubuntu, Debian, and CentOS 5+
** Not available on CentOS 5
^ Only available on x64

Commits

The new version differs by 18 commits.

  • 60fad5f 4.13.0
  • 43db915 Merge pull request #2768 from sass/release-4-13
  • 0c8d308 Update references for v4.13 release
  • f1cc0d3 Use GCC 6 for Node 12 binaries (#2767)
  • 3838eae Use GCC 6 for Node 12 binaries
  • e84c6a9 Merge pull request #2766 from saper/node-modules-79
  • 64b6f32 Node 13 support
  • 8d0acca Merge pull request #2753 from schwigri/master
  • b0d4d85 Fix broken link to NodeJS docs in README.md
  • 887199a Merge pull request #2730 from kessenich/master
  • b1f54d7 Fix #2614 - Update lodash version
  • 96aa279 Merge pull request #2726 from XhmikosR/master-xmr-typos
  • 8421979 Assorted typo fixes.
  • 2513e6a chore: Remove PR template
  • 7ab387c Merge pull request #2673 from abetomo/remove_sudo_setting_from_travis

There are 18 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

npm start fails because of error referencing gapi

I get the following when I try to run npm start.

[at-loader] Checking finished with 1 errors
Time: 3825ms
Asset Size Chunks Chunk Names
main.bundle.js 143 kB 0 [emitted] main
vendor.bundle.js 2.14 MB 1 [emitted] vendor

ERROR in multi (webpack)-dev-server/client?http://localhost:3000 webpack/hot/dev-server angular/angular.js angular-ui-router/release/angular-ui-router.js angular-sanitize/angular-sanitize.js eventemitter3 material-design-lite/material.css material-design-lite/material.js
Module not found: Error: Can't resolve 'material-design-lite/material.css' in '/Users/ttrentham/source/angularjs-typescript-webpack/src'
@ multi (webpack)-dev-server/client?http://localhost:3000 webpack/hot/dev-server angular/angular.js angular-ui-router/release/angular-ui-router.js angular-sanitize/angular-sanitize.js eventemitter3 material-design-lite/material.css material-design-lite/material.js

ERROR in multi (webpack)-dev-server/client?http://localhost:3000 webpack/hot/dev-server angular/angular.js angular-ui-router/release/angular-ui-router.js angular-sanitize/angular-sanitize.js eventemitter3 material-design-lite/material.css material-design-lite/material.js
Module not found: Error: Can't resolve 'material-design-lite/material.js' in '/Users/ttrentham/source/angularjs-typescript-webpack/src'
@ multi (webpack)-dev-server/client?http://localhost:3000 webpack/hot/dev-server angular/angular.js angular-ui-router/release/angular-ui-router.js angular-sanitize/angular-sanitize.js eventemitter3 material-design-lite/material.css material-design-lite/material.js

ERROR in [at-loader] ./src/tasks.service.ts:111:12
TS2304: Cannot find name 'gapi'.

Does this need gapi in the package.json?

Introduce `allowJs` and `checkJs` compiler options

The common scenario is to migrate existing code to TS and start with TSC to compile/check existing code before switching completely to TS.
Have you considered adding that option, so it could be used when migrating code to Angular?

Thanks!

An in-range update of uglifyjs-webpack-plugin is breaking the build 🚨

The devDependency uglifyjs-webpack-plugin was updated from 2.1.0 to 2.1.1.

🚨 View failing branch.

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

uglifyjs-webpack-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v2.1.1

2.1.1 (2018-12-27)

Bug Fixes

  • don't crash when no extracted comments (#387) (68ad71c)
Commits

The new version differs by 2 commits.

  • a3ac27a chore(release): 2.1.1
  • 68ad71c fix: don't crash when no extracted comments (#387)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of uglifyjs-webpack-plugin is breaking the build 🚨

The devDependency uglifyjs-webpack-plugin was updated from 2.1.3 to 2.2.0.

🚨 View failing branch.

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

uglifyjs-webpack-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v2.2.0

2.2.0 (2019-07-31)

Features

Commits

The new version differs by 3 commits.

  • eb73536 chore(release): 2.2.0
  • b1df135 feat: generate higher quality SourceMaps (#408)
  • 4ea1f0c chore(defaults): update (#407)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

The devDependency karma was updated from 3.1.1 to 3.1.2.

🚨 View failing branch.

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

karma is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v3.1.2

Bug Fixes

Features

Commits

The new version differs by 11 commits.

  • 7d4d347 chore: release v3.1.2
  • 5077c18 chore: update contributors
  • fb05fb1 fix(server): use flatted for json.stringify (#3220)
  • 2682bff feat(docs): callout the key debug strategies. (#3219)
  • 4e87902 fix(changelog): remove release which does not exist (#3214)
  • 30ff73b fix(browser): report errors to console during singleRun=false (#3209)
  • 5334d1a fix(file-list): do not preprocess up-to-date files (#3196)
  • dc5f5de fix(deps): upgrade sinon-chai 2.x -> 3.x (#3207)
  • d38f344 fix(package): bump lodash version (#3203)
  • ffb41f9 refactor(browser): log state transitions in debug (#3202)
  • 240209f fix(dep): Bump useragent to fix HeadlessChrome version (#3201)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

The devDependency node-sass was updated from 4.11.0 to 4.12.0.

🚨 View failing branch.

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

node-sass is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v4.12.0

Features

Community

Dependencies

Supported Environments

OS Architecture Node
Windows x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
OSX x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
Linux* x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**^, 12**^
Alpine Linux x64 6, 8, 10, 11, 12

*Linux support refers to Ubuntu, Debian, and CentOS 5+
** Not available on CentOS 5
^ Only available on x64

Commits

The new version differs by 19 commits.

  • 23c8659 4.12.0
  • bc78b22 Merge pull request #2633 from xzyfer/node-12
  • 12c0052 Workaround waiting for AppVeyor to add Node versions
  • 9e564a1 Use explicit Node version numbers in CI config
  • 5aae0d2 Use Visual Studio 2017 for Node >= 10
  • 480250c Use g++4.9 for all Node >= 10 in Travis CI
  • f4eebc8 Node 12 requires at least [email protected]
  • 34f99a2 Fix OSX compilation for Mojavi
  • da10866 Add support for Node 12
  • 0f86a0a Update README.md (#2617)
  • 33a32c3 https-ify sass-lang.com urls (#2608)
  • a2ac801 removed outdated TOC entries
  • 44366b3 Update lodash and remove prototype vulnerabilities
  • 088b80b Remove @adamyeats from maintainers list
  • 7c1dd8e Merge pull request #2454 from nschonni/troubleshooting-edits

There are 19 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

The devDependency jquery was updated from 3.3.1 to 3.4.0.

🚨 View failing branch.

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

jquery is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of fork-ts-checker-webpack-plugin is breaking the build 🚨

The devDependency fork-ts-checker-webpack-plugin was updated from 0.4.14 to 0.4.15.

🚨 View failing branch.

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

fork-ts-checker-webpack-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

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

Release Notes for v0.4.15
Commits

The new version differs by 1 commits.

  • 97c86d6 [Feature][#67] Adds tslint autofix as a flag to ForkTsCheckerWebpackPlugin plugin (#174)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

The devDependency @types/jquery was updated from 3.3.29 to 3.3.30.

🚨 View failing branch.

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

@types/jquery is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Why use angular-cli-tools instead of angular-cli?

I'm sorry to open this is an issue, but I'm really trying to understand if this recipe for building an NG 1.7 project is the best solution for us.

Is there a technical reason for using angular-cli-tools instead of angular-cli? I'm wanting to upgrade our NG 1.5 project to 1.7 and everything you've done so that migrating to NG7 will be simpler and possibly even piece meal.

Thanks!

An in-range update of angular-cli-tools is breaking the build 🚨

The devDependency angular-cli-tools was updated from 1.10.2 to 1.10.3.

🚨 View failing branch.

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

angular-cli-tools is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 4 commits.

  • 417c448 Merge pull request #25 from JoeFirebaugh/master
  • 3874364 Fixed README.md to call out defaultStyle usage.
  • 2d77d67 Updated dependant libs to remove Audit errors, and add defaultStyle option to user config.json.
  • 5f8fee4 Update README.md

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

The devDependency jasmine-core was updated from 3.4.0 to 3.5.0.

🚨 View failing branch.

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

jasmine-core is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 117 commits.

  • 99799f7 Still need some ruby stuff around to release the jasmine-core gem
  • e8263e3 bump version to 3.5.0
  • 53561ae Show details of syntax (etc) errors when loading Jasmine's own specs
  • 68f25a7 Don't create env instances in beforeEach
  • 96ba66a Built distribution
  • ba4a8d1 Fixed jsdocs
  • 65d9e93 Removed broken & long-disabled JsApiReporter integration specs
  • 2d3ac38 toBeRejectedWithError can expect the error to be Error, not just a subtype
  • 5a219da Added basic integration tests for all built-in matchers
  • f056f3b Fixed indentation
  • aeb0b73 Merge branch 'dtychshenko-1740-fail-on-no-expectations'
  • 7263a38 Adds new configuration option to failSpecWithNoExpectations that will report specs without expectations as failures if enabled
  • e8870db Merge branch 'fix-missing-asynchronous-stacktrace' of https://github.com/prantlf/jasmine into prantlf-fix-missing-asynchronous-stacktrace
  • 35d1508 Show argument diffs in toHaveBeenCalledWith failure messages
  • 19292e4 Stop testing against PhantomJS

There are 117 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

The devDependency @types/jasmine was updated from 3.3.12 to 3.3.13.

🚨 View failing branch.

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

@types/jasmine is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

There have been updates to the angular1 monorepo:

    • The dependency angular was updated from 1.7.8 to 1.7.9.
  • The devDependency angular-mocks was updated from 1.7.8 to 1.7.9.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the angular1 group definition.

angular1 is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

There have been updates to the angular1 monorepo:

    • The dependency angular was updated from 1.7.5 to 1.7.6.
  • The devDependency angular-mocks was updated from 1.7.5 to 1.7.6.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the angular1 group definition.

angular1 is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

The devDependency jasmine-core was updated from 3.3.0 to 3.4.0.

🚨 View failing branch.

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

jasmine-core is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 40 commits.

  • 8fca3b4 Fix links in 3.4 release notes
  • e636f5f Bump version to 3.4
  • 74fd0e0 No fit in the suite
  • 618e24b Handle WebSocket events in IE when detecting Errors
  • 5c7e25e Allow excluded specs in CI without breaking the output
  • 54af109 Merge branch 'wood1986-fix/npm-audit-dependencies-and-fast-glob-only-failed-tests'
  • 873a237 Consolidate some dev dependencies and use more maintained versions
  • 8ca4463 Make node execution default and override for browsers
  • 449eb51 Fix sauce status codes and try travis built-in node support
  • a5df5a6 Use the correct env var from travis for tunnels
  • be58323 bump dependencies for security fixes
  • d389d3c Merge branch 'wood1986-features/no-ruby'
  • 994d11d update node CI script to work with SauceLabs
  • 828d14f Use node.js for browser-based CI
  • f5663a9 Merge branch 'johnjbarton-duration'

There are 40 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.