Bug report

🐛 bug report

loadConfig should emit a codeframe on a parse error:

https://github.com/parcel-bundler/parcel/blob/2f6274311889cad76fbdf2dafe60fc23478476d6/packages/core/utils/src/config.js#L80

This is for example used for loading .postcssrc.

🤔 Expected Behavior

See screenshot in parcel-bundler/parcel#4420

😯 Current Behavior

With an invalid `.p

Hi, I've been trying to figure out from the docs (and google) to implement externalization of modules in Browserify with no luck. I've implemented transform-runtime plugins, and used .external(filename) in Gulp and tried to use require() in another module ... but I general cannot figure out from the docs what part or parts I'm missing in making this work.

Could someone please, add a brief secti

I'm testing out madge on my TS RN codebase, and I'm surprised to see that it just magically works without specifying a tsconfig.

For example
yarn madge --circular --extensions ts,tsx ./

Although this is cool and exciting, it gives me pause because the documentation doesn't explain how this works. I read the source and followed the path through a series of external npm dependencies. Af

I was expecting this configuration to work in can-route:

steal = {
	paths: {
		'src/routedata': 'src/routedata-definemap.js'
	}
};

Instead, I had to include can-route in the mapping:

steal = {
	paths: {
		'can-route/src/routedata': 'src/routedata-definemap.js'
	}
};

Is this expected? If so, can some more documentation around this be added?

It would be helpful to have tooltips or documentation to explain the significance of "weighted" vs. "size", and "dependants" vs "imports".

After encountering dependency-check-team/dependency-check#112 I tried looking into how that project uses detective and the various "extensions", such as detective-typescript that enabled foreign syntax. It was not immediately obvious how this worked, seeing no explicit interfaces where detective was wrapped by or passed some "extension"

Could

Related/original report: pahen/madge#117

It appears Precinct does not work with webpack's dynamic loading with require.context (basically glob) so e.g.

var context = require.context(".", true, /\.js$/)
context.keys().forEach(context)

This ought to load all the modules with /.js$/ from the curren

Is it possible to add support for debugging with the 'npm run dev' command?
I can't see to make it work using --inspect or --inspect -r ts-node/register Index.ts.

Maybe it's some issue with the combination of nodemon and ts-node.
Debugging support make it so easy to debug issues.

See the information in #133. It should be clearer in the example why the tools exist as they are and what the bare minimum setup is.