[RFC] re-export the "get-meta-file" package
See original GitHub issueTo simplify plugin development, make get-meta-file an implementation detail and re-export it in the meta package.
const getMetaFile = require('get-meta-file');
const { findConfig, readConfig } = require('meta');
assert(getMetaFile === readConfig);
assert(getMetaFile.getFileLocation === findConfig);
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Re-exporting C symbols for cdylib · Issue #2771 · rust-lang/rfcs
In an extern block, C symbols can be imported to Rust. When building Rust library into dylib, the symbols stay visible and can...
Read more >reexport controls - BIS.doc.gov
The United States Department of Commerce regulates exports and reexports of “dual-use” items, i.e., goods, software and technologies with commercial.
Read more >How to reexport `*` from a module that uses `export =`
How to re-export from a module that uses export= syntax? I have no control over the module with export= syntax. typescript.
Read more >Expansion of Export, Reexport, and Transfer (in-Country ...
The Bureau of Industry and Security (BIS) is amending the Export Administration Regulations (EAR) to expand license requirements on exports, ...
Read more >Re-exporting ES6 modules - James K Nelson
With the advent of Babel, ES6 modules have become a real option for organising code. Mapping your require statements to import and module....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Hah. I’m cool with it. Let’s just make sure we update docs to reflect it. We’ll want to get something simple in there as a reminder for when we beef up and redo the docs, at large.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.