geops / react-spatial Goto Github PK
View Code? Open in Web Editor NEWComponents to build React map apps
Home Page: https://react-spatial.geops.io
License: MIT License
Components to build React map apps
Home Page: https://react-spatial.geops.io
License: MIT License
3.5.0
to 3.6.0
.This version is covered by your current version range and after updating it in your project the build failed.
react-icons 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.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
We should try to find a component library, which provides basic building blocks so we don't have to reinvent the wheel for things like buttons, links and lists. At the same time we need a theming solution to make our components more flexible. Both solutions should meet the following requirements:
3.1.1
to 3.1.2
.This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-prettier 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.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
6.0.0-dev.1569533689380
to 6.0.0
.This version is covered by your current version range and after updating it in your project the build failed.
ol 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.
Wow. The 6.0 release includes changes from 1780 commits in 544 pull requests since the 5.3 release. Thanks to all who contributed to this effort.
A major feature in this release is the ability to compose layers with different renderer types. Previously, the map used a single rendering strategy, and all layers in your map had to implement that strategy. Now it is possible to have a map with layers that use different rendering technologies. This makes it possible, for example, to have Canvas (2D) layer composed together with a WebGL based layer in the same map. It is also possible to create layers with custom renderers. So you could have a map that uses another library (like d3) to render one layer and use OpenLayers to render the other layers. We will continue to take advantage of this new flexibility in future releases.
In addition, the 6.0 release includes a number of vector tile rendering improvements and should have a lower memory footprint overall. The release also includes a number of experimental features that are not yet part of the stable API. Take a look through the examples for a new WebGL based renderer and the experimental useGeographic()
function. Watch upcoming releases for more detail on these.
This release includes a number of backwards incompatible changes. Take a careful look at the notes below when upgrading your application from the 5.3 release.
map.forEachLayerAtPixel
Due to performance considerations, the layers in a map will sometimes be rendered into one
single canvas instead of separate elements.
This means map.forEachLayerAtPixel
will bring up false positives.
The easiest solution to avoid that is to assign different className
properties to each layer like so:
new Layer({ // ... className: 'my-layer' })
Please note that this may incur a significant performance loss when dealing with many layers and/or
targetting mobile devices.
TOUCH
constant from ol/has
If you were previously using this constant, you can check if 'ontouchstart'
is defined in window
instead.
if ('ontouchstart' in window) { // ... }
GEOLOCATION
constant from ol/has
If you were previously using this constant, you can check if 'geolocation'
is defined in navigator
instead.
if ('geolocation' in navigator) { // ... }
The CSS media print rules were removed from the ol.css
file. To get the previous behavior, use the following CSS:
@media print { .ol-control { display: none; } }
The optional this (i.e. opt_this) arguments were removed from the following methods.
Please use closures, the es6 arrow function or the bind method to achieve this effect (Bind is explained here:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/bind).
forEachCorner
in ol/extent
LRUCache#forEach
RBush#forEach
and RBush#forEachInExtent
setCenter
, setZoom
, setResolution
and setRotation
methods on ol/View
do not bypass constraints anymorePreviously, these methods allowed setting values that were inconsistent with the given view constraints.
This is no longer the case and all changes to the view state now follow the same logic:
target values are provided and constraints are applied on these to determine the actual values to be used.
constrainResolution
option on View.fit
, PinchZoom
, MouseWheelZoom
and ol/interaction.js
The constrainResolution
option is now only supported by the View
class. A View.setConstrainResolution
method was added as well.
Generally, the responsibility of applying center/rotation/resolutions constraints was moved from interactions and controls to the View
class.
extent
option now applies to the whole viewportPreviously, this options only constrained the view center. This behaviour can still be obtained by specifying constrainCenterOnly
in the view options.
As a side effect, the view rotate
method is gone and has been replaced with adjustRotation
which takes a delta as input.
Previously, maps showed multiple worlds at low zoom levels. In addition, it used to be possible to pan off the north or south edge of the world. Now, the view is restricted to show only one world, and you cannot pan off the edge. To get the previous behavior, configure the ol/View
with multiWorld: true
.
The inherits
function that was used to inherit the prototype methods from one constructor into another has been removed.
The standard ECMAScript classes should be used instead.
The deprecated getSnapToPixel
and setSnapToPixel
functions from the ImageStyle
class have been removed.
Previously, the internal tile coordinates used in the library had an unusual row order – the origin of the tile coordinate system was at the top left as expected, but the rows increased upwards. This meant that all tile coordinates within a tile grid's extent had negative y
values.
Now, the internal tile coordinates used in the library have the same row order as standard (e.g. XYZ) tile coordinates. The origin is at the top left (as before), and rows or y
values increase downward. So the top left tile of a tile grid is now 0, 0
, whereas it was 0, -1
before.
x, y values for tile coordinates
origin
*__________________________
| | | |
| 0, 0 | 1, 0 | 2, 0 |
||||
| | | |
| 0, 1 | 1, 1 | 2, 1 |
||||
| | | |
| 0, 2 | 1, 2 | 2, 2 |
|||________|
This change should only affect you if you were using a custom tileLoadFunction
or tileUrlFunction
. For example, if you used to have a tileUrlFunction
that looked like this:
// before function tileUrlFunction(tileCoord) { const z = tileCoord[0]; const x = tileCoord[1]; const y = -tileCoord[2] - 1; // do something with z, x, y }
You would now do something like this:
// after function tileUrlFunction(tileCoord) { const z = tileCoord[0]; const x = tileCoord[1]; const y = tileCoord[2]; // do something with z, x, y }
In addition (this should be exceedingly rare), if you previously created a ol/tilegrid/WMTS
by hand and you were providing an array of sizes
, you no longer have to provide a negative height if your tile origin is the top-left corner (the common case). On the other hand, if you are providing a custom array of sizes
and your origin is the bottom of the grid (this is uncommon), your height values must now be negative.
If you were previously using VectorTile
layers with renderMode: 'vector'
, you have to remove this configuration option. That mode was removed. 'hybrid'
(default) and 'image'
are still available.
If you were previously using Vector
layers with renderMode: 'image'
, you have to remove this configuration option. Instead, use the new ol/layer/VectorImage
layer with your ol/source/Vector
.
If a map has more than one layer with declutter
set to true, decluttering now considers all Vector
and VectorTile
layers, instead of decluttering each layer separately. Only VectorImage
layers continue to be decluttered separately. The higher the z-index of a layer, the higher the priority of its decluttered items.
Within a layer, the declutter order has changed. Previously, styles with a lower zIndex
were prioritized over those with a higher zIndex
. Now the opposite order is used.
On vector layers, even if decluttered images or texts have a lower z-Index than polygons or lines, they will now be rendered on top of the polygons or lines. For vector tile layers, this was the case already in previous releases.
prerender
and postrender
layer events replace old precompose
, render
and postcompose
eventsIf you were previously registering for precompose
and postcompose
events, you should now register for prerender
and postrender
events on layers. Instead of the previous render
event, you should now listen for postrender
. Layers are no longer composed to a single Canvas element. Instead, they are added to the map viewport as individual elements.
getVectorContext
function provides access to the immediate vector rendering APIPreviously, render events included a vectorContext
property that allowed you to render features or geometries directly to the map. This is still possible, but you now have to explicitly create a vector context with the getVectorContext
function. This change makes the immediate rendering API an explicit dependency if your application uses it. If you don't use this API, your application bundle will not include the vector rendering modules (as it did before).
Here is an abbreviated example of how to use the getVectorContext
function:
import {getVectorContext} from 'ol/render';// construct your map and layers as usual
layer.on('postrender', function(event) {
const vectorContext = getVectorContext(event);
// use any of the drawing methods on the vector context
});
Previously, it was possible to render a single layer in two maps. Now, each layer can only belong to a single map (in the same way that a single DOM element can only have one parent).
OverviewMap
requires a list of layers.Due to the constraint above (layers can only be added to a single map), the overview map needs to be constructed with a list of layers.
ol/Graticule
has been replaced by ol/layer/Graticule
Previously, a graticule was not a layer. Now it is. See the graticule example for details on how to add a graticule layer to your map.
ol/format/Feature
API changeThe getLastExtent()
method, which was required for custom tileLoadFunction
s in ol/source/Vector
, has been removed because it is no longer needed (see below).
ol/VectorTile
API changesgetProjection()
and setProjection()
methods. These were used in custom tileLoadFunction
s on ol/source/VectorTile
, which work differently now (see below).getExtent()
and setExtent()
methods. These were used in custom tileLoadFunction
s on ol/source/VectorTile
, which work differently now (see below).Previously, applications needed to call setProjection()
and setExtent()
on the tile in a custom tileLoadFunction
on ol/source/VectorTile
. The format's getLastExtent()
method was used to get the extent. All this is no longer needed. Instead, the extent
(first argument to the loader function) and projection
(third argument to the loader function) are simply passed as extent
and featureProjection
options to the format's readFeatures()
method.
Example for an old tileLoadFunction
:
function(tile, url) { tile.setLoader(function() { fetch(url).then(function(response) { response.arrayBuffer().then(function(data) { var format = tile.getFormat(); tile.setProjection(format.readProjection(data)); tile.setFeatures(format.readFeatures(data, { // featureProjection is not required for ol/format/MVT featureProjection: map.getView().getProjection() })); tile.setExtent(format.getLastExtent()); }) }) } });
This function needs to be changed to:
function(tile, url) { tile.setLoader(function(extent, resolution, projection) { fetch(url).then(function(response) { response.arrayBuffer().then(function(data) { var format = tile.getFormat(); tile.setFeatures(format.readFeatures(data, { // extent is only required for ol/format/MVT extent: extent, featureProjection: projection })); }) }) } });
The WebGL map and layers renderers are gone, replaced by a WebGLHelper
function that provides a lightweight,
low-level access to the WebGL API. This is implemented in a new WebGLPointsLayer
which does simple rendering of large number
of points with custom shaders.
This is now used in the Heatmap
layer.
The removed classes and components are:
WebGLMap
and WebGLMapRenderer
WebGLLayerRenderer
WebGLImageLayer
and WebGLImageLayerRenderer
WebGLTileLayer
and WebGLTileLayerRenderer
WebGLVectorLayer
and WebGLVectorLayerRenderer
WebGLReplay
and derived classes, along with associated shadersWebGLReplayGroup
WebGLImmediateRenderer
WebGLMap
mustache
and the Makefile
at the rootFollowing the removal of the experimental WebGL renderer, the AtlasManager has been removed as well. The atlas was only used by this renderer.
The non API getChecksum
functions of the style is also removed.
The ol/source/Vector#clear()
method no longer triggers a reload of the data from the server. If you were previously using clear()
to refetch from the server, you now have to use refresh()
.
The ol/source/Vector#refresh()
method now removes all features from the source and triggers a reload of the data from the server. If you were previously using the refresh()
method to re-render a vector layer, you should instead call ol/layer/Vector#changed()
.
getGetFeatureInfoUrl
to getFeatureInfoUrl
The getGetFeatureInfoUrl
of ol/source/ImageWMS
and ol/source/TileWMS
is now called getFeatureInfoUrl
.
getFeaturesAtPixel
always returns an arraygetFeaturesAtPixel
now returns an empty array instead of null if no features were found.
Hit detection over styled Circle geometry and Circle and RegularShape styles is now consistent with that for styled Polygon geometry. There is no hit detection over the interior of unfilled shapes. To get the previous behavior, specify a Fill style with transparent color.
It is now possible to configure vector tile layers with declutter: true
and renderMode: 'image'
. However, note that decluttering will be done per tile, resulting in labels and point symbols getting cut off at tile boundaries.
Until now, using both options forced the render mode to be hybrid
.
ol/PluggableMap
and subclasses no longer support the loadTilesWhileAnimating
and loadTilesWhileInteracting
options. These options were used to enable tile loading during animations and interactions. With the new DOM composition render strategy, it is no longer necessary to postpone tile loading until after animations or interactions.
layers
property as optional in OverviewMap constructor (@fredj)layerState
param from prepareFrame
and renderFrame
function (@fredj)@inheritDoc
) (@KaiVolland)~1.11.0
(@KaiVolland)There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
1.17.1
to 1.18.0
.This version is covered by your current version range and after updating it in your project the build failed.
prettier 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.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
2.16.0
to 2.17.0
.This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-import 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.
The new version differs by 61 commits.
0499050
bump to v2.17.0
f479635
[webpack] v0.11.1
8a4226d
Merge pull request #1320 from bradzacher/export-ts-namespaces
988e12b
fix(export): Support typescript namespaces
70c3679
[docs] make rule names consistent
6ab25ea
[Tests] skip a TS test in eslint < 4
405900e
[Tests] fix tests from #1319
2098797
[fix] export
: false positives for typescript type + value export
70a59fe
[fix] Fix overwriting of dynamic import() CallExpression
e4850df
[ExportMap] fix condition for checking if block comment
918567d
[fix] namespace
: add check for null ExportMap
2d21c4c
Merge pull request #1297 from echenley/ech/fix-isBuiltIn-local-aliases
0ff1c83
[dev deps] lock typescript to ~
, since it doesn’t follow semver
40bf40a
[*] [deps] update resolve
28dd614
Merge pull request #1304 from bradennapier/feature/typescript-export-type
There are 61 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
This lib should translation library agnostic. We should remove use of react-i18next from ShareMenu and Menu
3.4.0
to 3.5.0
.This version is covered by your current version range and after updating it in your project the build failed.
react-icons 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.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
2.4.0
to 2.4.1
.This version is covered by your current version range and after updating it in your project the build failed.
canvas 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.
The new version differs by 6 commits.
fea4c0d
2.4.1
e25a285
history: 2.4.1
22925d3
Merge pull request #1385 from LinusU/guard-jpeg-side
a1c31df
Guard JPEG width/height against maximum supported
3d81e0a
Fix Electron 5 and NodeJS 12 compatibility (#1383)
cb958e8
Fix missing encoding options (quality) parameter in canvas.toDataURL()
(#1382)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
devDependency
enzyme was updated from 3.8.0
to 3.9.0
.devDependency
enzyme-adapter-react-16 was updated from 1.11.2
to 1.12.0
.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 enzyme group definition.
enzyme 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.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
0.0.4-beta-3
to 0.0.4-beta.7
.This version is covered by your current version range and after updating it in your project the build failed.
ole 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.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
4.35.3
to 4.36.0
.This version is covered by your current version range and after updating it in your project the build failed.
webpack 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.
append
option now supports the default placeholders in addition to [url]
"..."
when overriding options.The new version differs by 42 commits.
95d21bb
4.36.0
aa1216c
Merge pull request #9422 from webpack/feature/dot-dot-dot-merge
b3ec775
improve merging of resolve and parsing options
53a5ae2
Merge pull request #9419 from vankop/remove-valid-jsdoc-rule
ab75240
Merge pull request #9413 from webpack/dependabot/npm_and_yarn/ajv-6.10.2
0bdabf4
Merge pull request #9418 from webpack/dependabot/npm_and_yarn/eslint-plugin-jsdoc-15.5.2
f207cdc
remove valid jsdoc rule in favour of eslint-plugin-jsdoc
31333a6
chore(deps-dev): bump eslint-plugin-jsdoc from 15.3.9 to 15.5.2
036adf0
Merge pull request #9417 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.8.0
37d4480
Merge pull request #9411 from webpack/dependabot/npm_and_yarn/simple-git-1.121.0
ce2a183
chore(deps-dev): bump eslint-plugin-jest from 22.7.2 to 22.8.0
0beeb7e
Merge pull request #9391 from vankop/create-hash-typescript
bf1a24a
#9391 resolve super call discussion
bd7d95b
#9391 resolve discussions, AbstractMethodError
4190638
chore(deps): bump ajv from 6.10.1 to 6.10.2
There are 42 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
9.1.4
to 9.1.5
.This version is covered by your current version range and after updating it in your project the build failed.
react-styleguidist 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.
Fixed: to make async/await work by default (#1379)
Add transforms: { asyncAwait: false } for default compilerConfig to make async/await work by default. Bublé doesn't have transform for async/await so they raise an error if asyncAwait transformation in configuration is not false (true by default) since bublé v0.9.7.
Closes #1371
The new version differs by 1 commits.
9c71f1f
Fix: to make async/await work by default (#1379)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
2.18.2
to 2.19.0
.This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-import 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.
The new version differs by 46 commits.
9b76635
Bump to v2.19.0
47a232e
[resolvers/webpack] v0.12.0
26ad476
[resolvers/webpack] [deps] update debug
, enhanced-resolve
, has
, interpret
, lodash
, resolve
, semver
3f0e8f3
[resolvers/node] [Deps] update resolve
7190c3e
bump utils to v2.5.0
a60e5c6
[New] no-commonjs
: add allowConditionalRequire
option
414c923
[New] enable passing cwd as an option to eslint-import-resolver-webpack
8224e51
[New] order
/no-extraneous-dependencies
: Alphabetize imports within groups
f12ae59
[New] no-duplicates
: add a considerQueryString option to handle false positives when using some webpack loaders.
2d3d045
[fix] importType
: Accept '@example' as internal
0426f16
[New] order
: add pathGroups option to add support to order by paths
99b3fbf
[Fix] no-extraneous-dependencies
: Add support for export from
21bf8c6
[Fix] no-cycle
: should not warn for Flow imports
0cd5e43
[Fix] no-unused-modules
: fix crash due to export *
05085bb
[flow] no-unused-modules
: add flow type support
There are 46 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Very useful library! It looks like you have a lot here and I'm curious about the runway to first release. Are there major features that you are looki.mapng to add before graduating from Beta or are there stability issues that need addressing?
1.0.1
to 1.0.2
.This version is covered by your current version range and after updating it in your project the build failed.
style-loader 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.
The new version differs by 4 commits.
7768fce
chore(release): 1.0.2
dcbfadb
fix: support ES module syntax (#435)
d515edc
chore(deps): update (#434)
4c1e3f3
docs: fixed typo 'doom' to 'DOM' in README.md (#432)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
7.14.3
to 7.15.0
.This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-react 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.
The new version differs by 30 commits.
b45219a
Update CHANGELOG and bump version
a01198f
[Dev Deps] update eslint-config-airbnb-base
, eslint-plugin-import
, sinon
, typescript
ab77870
[Deps] update jsx-ast-utils
, resolve
32e27b7
[Fix] jsx-indent
: Fix false positive when a jsx element is the last statement within a do expression (with tests)
628a4a0
[fix] jsx-curly-brace-presence
: fix jsx tags in braces
3124ce0
[Docs] no-access-state-in-setstate
: update grammar
4a05fa2
[fix] display-name
: Fix false positives
c6521ad
Change istanbul output directory to ./coverage (default)
5970651
[new] jsx-handler-name
: allow false
to disable eventHandlerPrefix
/eventHandlerPropPrefix
489ced3
[refactor] jsx-curly-braces-presence, jsx-one-expression-per-line, no-danger-with-children
: add isWhiteSpaces
to lib/util/jsx
9b2db61
[fix] jsx-curly-brace-presence
: report unnecessary curly braces with children on next line
781bfff
[new] sort-comp
: add static-variables
grouping
7ccff10
[New] add jsx-no-useless-fragment
rule
66725bc
[Fix] no-unused-prop-types
: false positive with callback
3c72a49
[eslint] disable some options and manually fix valid-jsdoc
There are 30 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
9.1.5
to 9.1.6
.This version is covered by your current version range and after updating it in your project the build failed.
react-styleguidist 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.
The new version differs by 2 commits.
5ff72d8
Fix: Fix named export for example components (#1380)
7f6a77c
Chore: Add Sponsor GitHub button
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
1.18.2
to 1.19.0
.This version is covered by your current version range and after updating it in your project the build failed.
prettier 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.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.