-
@1egoman
Now (same setup as in https://github.com/1egoman/debundle/issues/5), when I run the command:
```
debundle -i public/assets/frontend/js/modules/scripts.js -o public/assets/frontend/js/mod…
-
Hello @1egoman,
Commands I run triggering the issue:
```
debundle -i public/assets/frontend/js/modules/scripts.js -o public/assets/frontend/js/modules/unpacked/ -c public/assets/frontend/js/modul…
-
In order to troubleshoot, I need:
- A bundle that doesn't work, preferably as minimal as possible.
- Your configuration that you passed with the `-c` argument when debundling.
- The **EXACT** com…
-
In [this mail](https://mail.python.org/pipermail/pytest-dev/2015-August/003103.html), @nicoddemus said:
> I think Holger also said before that he would like to vendor pluggy into
> pytest before rele…
-
Given a bundle that contains this module:
```javascript
function(a, b, c) {
a.foo = 1; // Used as expected
{
// A different scope!
let a = 5;
a = 6;
};
}
```
This proje…
-
-
This is a bundled term and should be debundled
-
And prompt to remove the old JB plugin.
Depends on #767. Needed only until old plugin is debundled from IJ.
-
Golang packages are built for epel7 as well. The with_devel and other macros must take that into account and enable devel and unit-test packages as well.
Let's discuss what is the best resolution for…
-
After updating from 0.5.1.0 to 0.5.3.0 I got error:
```
diaspora@np:~/diaspora$ DB=postgres bin/rake db:migrate
rake aborted!
NameError: uninitialized constant ActionView::Helpers::ActiveModelHelper
…