chungchi300

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

var Article = require('../../../models/article');

Those suck for maintenance and they're ugly.

Possible solutions

chungchi300

//very important,these javascript component  is more debuggable then native
import fetch from 'isomorphic-fetch';
import FormData from 'form-data';

let formData = new FormData();
formData.append('file',fs.createReadStream('test/api/testMedia.jpg'));

//implement your own header function
let headers = prepareHeaders();

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

appastair

jQuery(function($){
    $.ajax({
        type: 'GET',
        url: '//remote.org/jsonp.php',
        data: {
            field: 'value'
        },
        dataType: 'jsonp'
        crossDomain: true,
    }).done(function(response){