Skip to content

Latest commit

 

History

History
66 lines (59 loc) · 2.54 KB

README.md

File metadata and controls

66 lines (59 loc) · 2.54 KB

import-directory Build Status

Same as require-directory

But support to use import and export default syntax in your file inside the directory.

## Install

npm install --save require-directory import-directory

How it works

If we use export default inside the directory with require-directory, the result will become like that..

```javascript { model1: { default: { name: 'Model1' } }, model2: { default: { name: 'Model2' } } } ```

Because export default is same as module.exports = {default: ....}.

But what we want is

```javascript { model1: { name: 'Model1' }, model2: { name: 'Model2' } } ```

The logic behind is just change the 'visit' option provided by require-directory.

Note: There the object that export other than export default like export {... as ...} or just export .... will be ignored.

How to use

as usual as require-directory, but change the import statement ```javascript import importDirectory from 'import-directory'; export default importDirectory(module); ```

LICENSE

The MIT License (MIT)

Copyright (c) 2016 Sze Ka Wai Raymond

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.