[Packager] Requiring json file failed

[meetwudi]

I have one config.json in the app directory, and also a List.js.

In List.js, it tries to load config.json using require (which is common in node.js). But it failed.

[jaygarcia]

I've had similar issues. I think it might have to be w/ the fact that the CommonJS implementation is not a full implementation for this framework.

[ericvicenti]

This would be nice to support.

Internally, we would just rename to .js and add a module.exports = to make it a normal JS module.

cc @amasad

[amasad]

This landed internally, should land here next sync.

[alexaivars]

would this be the same issue as trying todo require('./package') resulting in 'unknown module' ?

[brentvatne]

@alexaivars - if when you do that you are trying to require package.json then yup, same thing

[alexaivars]

awesome, hope the next sync lands soon.

[amasad]

I didn't know that require('./package') resolved to package.json. I think it just works for hard coded .json files. @alexaivars can you confirm that it doesn't work?

[alexaivars]

@amasad I can confirm that this is true and that it's a quite common practice to require package.json in this fashion. I however first noticed this since react-native chocked when I required cheerio.

[paulgessinger]

Any news on this front?

I found that most scrapers seem to require some package that does this doe there is not much to be gained by switching to another library. #231 says the JSON requiring bug was fixed, yet I'm still getting errors with 0.4.4

[amasad]

@paulgessinger Yeah, require('./package.json') works, no?
The issue @alexaivars is explaining is omitting the "json".

[amasad]

Fixed this internally, should land next sync.

[cgarvis]

+1