ckarper / asar-fs Goto Github PK

View Code? Open in Web Editor NEW

8.0 8.0 1.0 117 KB

A rudimentary fs monkeypatch to support loading files and modules from an atom/asar archive.

License: MIT License

JavaScript 100.00%

archive asar asar-archive filesystem monkey-patching node npm

asar-fs's People

Contributors

Stargazers

Watchers

Forkers

hrundik

asar-fs's Issues

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

Version 3.17.0 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	3.16.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v3.17.0

4fdf6d7 Update: deprecate applyDefaultPatterns in line-comment-position (#8183) (alberto)
25e5817 Fix: Don't autofix + +a to ++a in space-unary-ops (#8176) (Alan Pierce)
a6ce8f9 Build: Sort rules before dumping them to doc files (#8154) (Danny Andrews)
0af9057 Chore: Upgrade to a patched version of mock-fs (fixes #8177) (#8188) (Teddy Katz)
bf4d8cf Update: ignore eslint comments in lines-arount-comment (fixes #4345) (#8155) (alberto)
dad20ad New: add SourceCode#getLocFromIndex and #getIndexFromLoc (fixes #8073) (#8158) (Teddy Katz)
18a519f Update: let RuleTester cases assert that no autofix occurs (fixes #8157) (#8163) (Teddy Katz)
a30eb8d Docs: improve documentation for RuleTester cases (#8162) (Teddy Katz)
a78ec9f Chore: upgrade coveralls to ^2.11.16 (#8161) (alberto)
d02bd11 Fix: padded-blocks autofix problems with comments (#8149) (alberto)
9994889 Docs: Add missing space to create in no-use-before-define (#8166) (Justin Anastos)
4d542ba Docs: Remove unneeded statement about autofix (#8164) (alberto)
20daea5 New: no-compare-neg-zero rule (#8091) (薛定谔的猫)
4d35a81 Fix: Add a utility to avoid autofix conflicts (fixes #7928, fixes #8026) (#8067) (Alan Pierce)
287e882 New: nonblock-statement-body-position rule (fixes #6067) (#8108) (Teddy Katz)
7f1f4e5 Chore: remove unneeded devDeps linefix and gh-got (#8160) (alberto)
ca1694b Update: ignore negative ranges in fixes (#8133) (alberto)
163d751 Docs: lines-around-comment doesn't disallow empty lines (#8151) (alberto)
1c84922 Chore: upgrade eslint-plugin-node (#8156) (alberto)
1ee5c27 Fix: Make RuleTester handle empty-string cases gracefully (fixes #8142) (#8143) (Teddy Katz)
044bc10 Docs: Add details about "--fix" option for "sort-imports" rule (#8077) (Olivier Audard)
3fec54a Add option to ignore property in no-param-reassign (#8087) (Christian Bundy)
4e52cfc Fix: Improve keyword-spacing typescript support (fixes #8110) (#8111) (Reyad Attiyat)
7ff42e8 New: Allow regexes in RuleTester (fixes #7837) (#8115) (Daniel Lo Nigro)
cbd7ded Build: display rules’ meta data in their docs (fixes #5774) (#8127) (Wilson Kurniawan)
da8e8af Update: include function name in report message if possible (fixes #7260) (#8058) (Dieter Luypaert)
8f91e32 Fix: ignoreRestSiblings option didn't cover arguments (fixes #8119) (#8120) (Toru Nagashima)

Commits

The new version differs by 29 commits .

f882a11 3.17.0
6748c18 Build: package.json and changelog update for 3.17.0
4fdf6d7 Update: deprecate applyDefaultPatterns in line-comment-position (#8183)
25e5817 Fix: Don't autofix + +a to ++a in space-unary-ops (#8176)
a6ce8f9 Build: Sort rules before dumping them to doc files (#8154)
0af9057 Chore: Upgrade to a patched version of mock-fs (fixes #8177) (#8188)
bf4d8cf Update: ignore eslint comments in lines-arount-comment (fixes #4345) (#8155)
dad20ad New: add SourceCode#getLocFromIndex and #getIndexFromLoc (fixes #8073) (#8158)
18a519f Update: let RuleTester cases assert that no autofix occurs (fixes #8157) (#8163)
a30eb8d Docs: improve documentation for RuleTester cases (#8162)
a78ec9f Chore: upgrade coveralls to ^2.11.16 (#8161)
d02bd11 Fix: padded-blocks autofix problems with comments (#8149)
9994889 Docs: Add missing space to create in no-use-before-define (#8166)
4d542ba Docs: Remove unneeded statement about autofix (#8164)
20daea5 New: no-compare-neg-zero rule (#8091)

There are 29 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

How do you compact dependencies into an asar if there are so many dependencies?

So, I'm somewhat confused how this might be managed in terms of turning node_modules into an asar archive.

That is: I've generated an asar archive. Great. BUT asar-fs lists asar as a dependency, and asar itself has a significant list of dependencies. So... do you get what I'm getting at? How can I use asar-fs with node_modules, if my node_modules are in an .asar file? I know that I can exclude the /asar-fs module from the ASAR file, but what about its dependencies, and its dependencies dependencies etc? What's the correct approach here?

An in-range update of eslint is breaking the build 🚨

Version 3.17.1 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	3.17.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v3.17.1

f8c8e6e Build: change mock-fs path without SSH (fixes #8207) (#8208) (Toru Nagashima)
f713f11 Fix: nonblock-statement-body-position multiline error (fixes #8202) (#8203) (Teddy Katz)
41e3d9c Fix: operator-assignment with parenthesized expression (fixes #8190) (#8197) (alberto)
5e3bca7 Chore: add eslint-plugin-eslint-plugin (#8198) (Teddy Katz)
580da36 Chore: add missing output property to tests (#8195) (alberto)

Commits

The new version differs by 7 commits .

af8f8b9 3.17.1
a6c12f3 Build: package.json and changelog update for 3.17.1
f8c8e6e Build: change mock-fs path without SSH (fixes #8207) (#8208)
f713f11 Fix: nonblock-statement-body-position multiline error (fixes #8202) (#8203)
41e3d9c Fix: operator-assignment with parenthesized expression (fixes #8190) (#8197)
5e3bca7 Chore: add eslint-plugin-eslint-plugin (#8198)
580da36 Chore: add missing output property to tests (#8195)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of coveralls is breaking the build 🚨

Version 2.12.0 of coveralls just got published.

Branch	Build failing 🚨
Dependency	coveralls
Current Version	2.11.16
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As coveralls is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

Branch coverage support

Adds branch coverage data to Coveralls API post.

Commits

The new version differs by 2 commits .

d571dac merge, version bump
1575050 branching WIP

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 10.2.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	10.1.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits .

455619f chore(release): 10.2.0
95cc09a feat: upgrade to version of yargs with extend support (#541)
43535f9 chore: explicit update of istanbuljs dependencies (#535)
98ebdff feat: allow babel cache to be enabled (#517)
50adde4 feat: exclude the coverage/ folder by default 🚀 (#502)
6a59834 chore(package): update tap to version 10.0.0 (#507)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of babel-preset-env is breaking the build 🚨

Version 1.2.1 of babel-preset-env just got published.

Branch	Build failing 🚨
Dependency	babel-preset-env
Current Version	1.2.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-preset-env is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v1.2.1

v1.2.1 (2017-03-06)

🐛 Bug Fix

Add transform-duplicate-keys mapping (#192) (@existentialism)

Our plugin data was missing a mapping for the transform-duplicate-keys plugin which caused it to never be included. (s/o to @Timer for the report!)

📝 Documentation

Clarify reasons for the uglify option in README.md (#188) (@mikegreiling)

Commits

The new version differs by 4 commits .

14b2e4f v1.2.1 changelog [skip ci]
e407ea4 1.2.1
e4d0040 Add transform-duplicate-keys mapping (#192)
0465a63 Clarify reasons for the uglify option in README.md (#188)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

ckarper / asar-fs Goto Github PK

asar-fs's People

Contributors

Stargazers

Watchers

Forkers

asar-fs's Issues

Version 10 of Node.js (code name Dubnium) has been released! 🎊

Version 3.17.0 of eslint just got published.

Version 3.17.1 of eslint just got published.

Version 2.12.0 of coveralls just got published.

Version 10.2.0 of nyc just got published.

Version 1.2.1 of babel-preset-env just got published.

v1.2.1 (2017-03-06)

🐛 Bug Fix

📝 Documentation

Recommend Projects

Recommend Topics

Recommend Org