Version 1.0.3 of d3-array just got published.

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

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

Your Greenkeeper Bot 🌴

The dependency d3-selection was updated from 1.3.2 to 1.4.0.

🚨 View failing branch.

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

d3-selection 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.

Your Greenkeeper Bot 🌴

• confirm it does not conflict with other packages
• update documentation template

Localization is something that we've supported in the past that has not been properly addressed in the new version of d3plus. D3 contains some great time formatters, so let's implement a solution that combines any built-ins we can find with more specific word localizations (like the text for the "back" button).

My current idea is to have a global locale object exported by this module, and that object would contain keys for each language, which then in turn contain keys for specific types of localizations. An example format is here:

export default {
  "en-US": {
    time: {...}, // object imported from d3-time-format
    text: {
      back: "Back",
      ...
    }
  },
  "es-ES": {
    time: {...}, // object imported from d3-time-format
    text: {
      back: "Volver",
      ...
    }
  }
}

This object would be created in src/locale/index.js, importing all of the d3-time-format language modules, and importing our own modules from files like src/locale/text/es-ES.js. We would then add a .locale("es-ES") method to BaseClass so that every component can support localization.

@cnavarreteliz, @nbond211, thoughts?

The dependency d3-transition was updated from 1.1.3 to 1.2.0.

🚨 View failing branch.

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

d3-transition 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.

Your Greenkeeper Bot 🌴

Expected Behavior

Would be great if when setting a config method that is not supported, a console message should be displayed warning the user. Would be a modification of the logic here regarding k in this.

Current Behavior

Non-supported config keys silently fail.

for example:

accessor("height", 200);

would return:

function(d) {
  return d.height || 200;
}

things like .estlintrc and .travis.yml could be created/updated using a script like:

npm run env

This locale method would be stored internally as this._locale, and accept either a fully-constructed lanaguage object (referenced here) or a string that would be used to look up the default object the master list exported from that reference issue.

Expected Behavior

Currently, the color functions like colorAssign and colorContrast used for labels and fill colors use the default color object from d3plus-color, but have the ability to be overridden. When using these functions in Viz and Shape classes, there should be a method to allow the user to override the defaults.

Current Behavior

There currently is no way to overwrite them!

Hi,

Thanks for all of the work on this, we're having a slight issue with 0.6.50.

The latest release of d3plus-common (0.6.50) has not been babelified (or whatever you are using to make it es5 compatible?).

https://registry.npmjs.org/d3plus-common/-/d3plus-common-0.6.50.tgz

Version 0.6.49 was.

https://registry.npmjs.org/d3plus-common/-/d3plus-common-0.6.49.tgz

If you unzip them both you can see the difference.

We have pinned to 0.6.49 for now but just to let you know :)

Version 1.1.0 of d3-transition just got published.

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

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

Your Greenkeeper Bot 🌴

Version 1.0.5 of d3-selection just got published.

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

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

Your Greenkeeper Bot 🌴

The dependency d3-array was updated from 1.2.4 to 1.3.0.

🚨 View failing branch.

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

d3-array 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.

Your Greenkeeper Bot 🌴

Similar to the <> notation used in d3's docs:

Version 0.4.9 of d3plus-dev just got published.

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

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

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

Your Greenkeeper Bot 🌴

I get this message with or without updated deps

$ npm run-script build

> [email protected] build /home/pacha/github/d3plus-common
> d3plus-build




    d3plus-common v0.6.44
    build compile


[ done ] transpiling ES6 for modules
[ done ] bundling build/d3plus-common.js
[ fail ] CompileError: for...of statements are not supported. Use `transforms: { forOf: false }` to skip transformation and disable this error, or `transforms: { dangerousForOf: true }` if you know what you're doing (7:4)
3 :   let delta;
4 :   let mean = 0;
5 :   let sum = 0;
6 :   if (valueof === undefined) {
7 :     for (let value of values) {

The devDependency d3plus-dev was updated from 0.6.9 to 0.6.10.

🚨 View failing branch.

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

d3plus-dev 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.

Your Greenkeeper Bot 🌴

Hi,

Would it be possible to move dependencies that the end npm package user doesn't need to devDependencies. Now this package is forcing to install Electron (over 250 MB), Browserify, Babelify, ESLint, LiveServer, Faucet, Rollup, Tape, UglifyJS etc. for nothing.

Or is it that d3plus-common and d3plus-text should not be used via npm?

We updated to version 0.6.53 and noticed that the new dependency of locale-codes is ES6.
This is causing problems similar to #100 with ES5 compatibility.

Not a problem as we have pinned to an older version but wanted to make you aware.

Many thanks :)