Version 3.4.0 of uglify-js was just published.

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

uglify-js 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 🌴

Version 0.18.4 of size-limit was just published.

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

size-limit 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 🌴

Version 8.0.2 of documentation was just published.

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

documentation 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 🌴

Currently, all the Jimple's documentation refer to a..README file.

I think it's important to add a nice API documentation so any user can browse it and know more of it's internals.

By the way, probably that API documentation will be made using JSDoc.

I think a site is good to show all the Jimple's features, and allow the user to test it directly in it.

Currently GeneratorFunction objects are passing like normal function objects. The check Object.prototype.toString.call(fn) returns '[object Function]' in both cases. When a service is retrieved the instance is a generator object which is not probably correct. The solutions I can think of are:

• treat GeneratorFunction as simple parameter and not as service (ie typeof fn === 'function' && fn.constructor.name === 'Function)
• Find something neat to do woth generators (ie Factories could be implemented with a generator by yielding results every time the service is asked for and implement Jimple#factory() with a function *(c) { while(true) yield fn(c); })

🚨 You need to enable Continuous Integration on all 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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Hey.

The internal "isFunction" function is not compatible with IE11, on which "fn.constructor.name" will return undefined. Causing this library doesn't work at all on IE11

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.

Your Greenkeeper Bot 🌴

The devDependency mocha was updated from 6.0.1 to 6.0.2.

🚨 View failing branch.

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

mocha 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 🌴

The devDependency karma-firefox-launcher was updated from 1.1.0 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.

karma-firefox-launcher 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 🌴

Version 16.2.1 of browserify was just published.

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

browserify 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 🌴

The devDependency codacy-coverage was updated from 3.1.0 to 3.2.0.

🚨 View failing branch.

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

codacy-coverage 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 🌴

Version 3.4.1 of uglify-js was just published.

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

uglify-js 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 🌴

Version 0.12.1 of size-limit was just published.

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

size-limit 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 guys,

I sadly discovered that Jimple is not compatible with "create-react-app". It make the build fail with the following error :

Failed to minify the code from this file:

   ./node_modules/jimple/src/Jimple.js:45

Read more here: http://bit.ly/2tRViJ9

Any idea about how to fix it ?

I've been adding a file for another package which uses this one and I notice that jimple doesn't have its own TS types declaration file. If you want @fjorgemota I can make a PR to add what I've written for this package.

The devDependency browserify was updated from 16.2.3 to 16.3.0.

🚨 View failing branch.

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

browserify 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 🌴

The devDependency uglify-js was updated from 3.5.10 to 3.5.11.

🚨 View failing branch.

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

uglify-js 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 🌴

The devDependency karma-browserify was updated from 6.0.0 to 6.1.0.

🚨 View failing branch.

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

karma-browserify 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 🌴

Why to make hundred the same things in NPM ?

I have written https://github.com/avighier/simple-dijs begin 2015, why to write the same 1000 times ?

I don't understand the work, the time we can spend is for nothing ?? Can you help me to understand ??

Have a good day.

Seems like Jimple has some new friends, that add new features to the package, like frozen-jimple, which extends the class and customizes it as shown in our README.

So..should we add a plugin/middleware support directly to the package? It's just an idea for now, suggestions are accepted.

The whole thing with ansi-styles (npm/npm#17723) messed up a few of my apps with Jimple. As a fix, I pointed the version on the package.json to this repo last commit, but I would prefer using a version from the registry :P.

Btw, thanks a lot for the package, pretty useful!
Regards

Hi,

I have a proposal for a tiny improvement and I would like to check before sending a PR.

Here it is:

module.exports.provider = register => ({ register });

It may look silly, but I always end up creating this function on every Jimple project (and I have a few). I prefer this wrapper over having to define an object with a register method and exporting a generic register method.

Here's an example of how I use it:

const { provider } = require('...');

class MyService {
  constructor(dep1, dep2) {
    ...
  }
}

const myService = provider((c) => {
  container.set('myService', () => new MyService(
    c.get('dep1'),
    c.get('dep2')
  );
});

module.exports = {
  MyService,
  myService,
};

That way I make available the service class and the provider for it.

Let me know what you think; if you don't like it or you don't see any added value, no worries :). And if you like it, I'll send you the PR right away.

Regards.

The devDependency mocha was updated from 6.1.4 to 6.2.0.

🚨 View failing branch.

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

mocha 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 🌴

I used to user async function as instance providers, as is :

ioc.set('conf', async() => { return someInstance });

When i use it inside a REACT project, it's working fine, but not when i use it on server side. It may be due to babel or webpack compilation.

What about adding support for async function ? I wrote a small pull request which should do the job (not tested)