Giter VIP home page Giter VIP logo

syrian-heritage's Introduction

syrian-heritage

Explore Syrian heritage sites.

npm version build status dependency status dev dependency status

Contributing

If you have a question, found a bug or want to propose a feature, have a look at the issues page.

syrian-heritage's People

Contributors

derhuerst avatar greenkeeper[bot] avatar oliolsen0815 avatar

Stargazers

Nina Breznik avatar

Watchers

 avatar  avatar

Forkers

oliolsen0815

syrian-heritage's Issues

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

Version 3.7.0 of redux just got published.

Branch Build failing 🚨
Dependency redux
Current Version 3.6.0
Type devDependency

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

As redux 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 v3.7.0

Another long break!

Oh, hey! I didn't see you sitting there. You look bored. How about a Redux release to spice things up?

Not a huge set of changes to report here. The biggest change, and the reason for the minor bump, is the UMD build is now done via Rollup. One big advantage is more readable code in the bundle. Rollup does "scope hoisting", which is a fancy term for putting every module at the top level of the file. Other than a surrounding IIFE, all of the code in Redux all lives together. You can compare the two here:

Rollup UMD build
vs
Webpack UMD build

There is also a cost savings of 30,811 vs 26,880 bytes, and 6,999 vs 5,995 bytes minified. Redux is already a small library, and this helps shave some extra bytes for our UMD users.

One thing to note is that Webpack has introduced it's own scope hoisting feature in 3.0 beta. So, this isn't intended as an indictment of Webpack. You should continue to use it in your own apps. The adage of "Webpack is for apps, Rollup is for libraries" definitely holds true. It still has a superior developer experience with hot module reloading and webpack-dev-server. But use whatever makes sense for your project, not just whatever we use. πŸ˜„

We're also looking at applying this to the NPM bundle. The main motivation is again more readable code in your bundles. Instead of transpilation oddities from Babel, you will end up with a single clean file, which should be easier to read through and debug. It's currently scheduled for the big, mythical 4.0 release and you can follow along in #2358

Changes

Commits

The new version differs by 309 commits.

  • 2d229f0 3.7.0
  • f3bba96 Removing the browser field for now
  • f4d9e55 Upgrade all example deps, including the universal example to Webpack 2
  • 2bc8f84 Upgrade some other deps
  • 070b838 Upgrades and remove check-es3-syntax since Rollup breaks it always
  • 1094724 Fix a typo in the Immutable.js docs (#2453)
  • bf3a557 Fix redux-mock-store libdef for todos-flow (#2430)
  • bf2b9b5 give redux-subscriber some attention in StoreSetup.md (#2433)
  • 8b3e0cb syncing docs with recent PR (2431) (#2432)
  • e238a19 'todo' const removal from reducers/todos.js (#2431)
  • 0babfab Merge pull request #2429 from alexbaumgertner/bugfix/doc-link
  • ae563c3 Fix link to ImmutableData article
  • 383215a Update redux.js (#2428)
  • c9ad6a4 Add 100% test coverage for todos-flow example (#2413)
  • ea16d76 Fix eslint warnings, update react-scripts (#2420)

There are 250 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 uglify-es is breaking the build 🚨

Version 3.3.5 of uglify-es was just published.

Branch Build failing 🚨
Dependency uglify-es
Current Version 3.3.4
Type devDependency

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

uglify-es 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 v3.3.5

Β 

Commits

The new version differs by 34 commits.

  • 1f3f8f2 harmony-v3.3.5
  • 4b1799e disable reminify()
  • 7a8eff6 Merge branch 'master' into harmony-v3.3.5
  • 9336cc8 v3.3.5
  • 9809567 improve process.exit() workaround (#2741)
  • 1ee8be8 fix recursive function inline (#2738)
  • 8430c2f enable AppVeyor CI (#2739)
  • 659c8a7 handle trailing line comments correctly (#2736)
  • 3564b4f compress RegExp() in unsafe (#2735)
  • 3505a36 enhance unsafe_proto (#2733)
  • 9b1bc6c ufuzz: add strings "a", "b", "c" to VALUES (#2732)
  • 9f23185 fix corner case with arguments as function name (#2729)
  • b82feb9 improve if_return (#2727)
  • 7f2a591 warn on deprecated features (#2726)
  • f76b5e0 fix hoist_props on const (#2724)

There are 34 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 history is breaking the build 🚨

Version 4.7.0 of history just got published.

Branch Build failing 🚨
Dependency history
Current Version 4.6.3
Type devDependency

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

As history 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.

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 🌴

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.