Comments (7)
@davidtheclark what's blocking me from fixing this is the tests failing from a clean state on master when I clone and run yarn install
on my system with the latest stable node (v7.4.0 at time of writing). Does this package depend on a specific version of node?
I noticed that node v0.12 support was added recently even though the LTS support dropped as of December. Are there plans to move forward again?
- regardless, I'm quite sure that the tests should be written in ES2015+ since AVA transpiles them anyway.
from cosmiconfig.
@JaKXz How are the tests failing? What is the error? Have you tried seeing if the tests pass on Travis with Node 7 (by changing the .travis.yml
file in a PR)?
I just tried rm -rf node_modules && yarn install && npm test
and had no problem. I am on Node v4.7.0, Yarn v0.18.1.
Does this package depend on a specific version of node?
As specified in the package.json
, this package should work on Node 0.12 and higher.
I noticed that node v0.12 support was added recently
It was re-added, because we removed support but then some users wanted it back, and it was easy to restore.
Are there plans to move forward again?
I don't understand "move forward" here. There shouldn't be a problem with higher versions of Node. Maybe your error message will clarify things.
I'm quite sure that the tests should be written in ES2015+ since AVA transpiles them anyway.
I disagree. I'd rather have the codebase stick to one feature set than write the tests differently than the rest of the code.
from cosmiconfig.
@davidtheclark the failures are here: https://travis-ci.org/davidtheclark/cosmiconfig/jobs/189389524
I had spent some time a few weeks ago attempting to debug the failures locally but made no progress without context. I suppose I'll make a separate issue about the tests failing on node v7 (done: #53).
re:
I'd rather have the codebase stick to one feature set than write the tests differently than the rest of the code
using t
for all assertions is the compromise that I'm suggesting, then.
from cosmiconfig.
You have to name the variable t
? That is stupid. I wonder if these other failures are also caused by AVA bugs. At some point I'll try switching to tape to see what happens on Node 7. Or if you want to speed things along, feel free to give that a shot.
from cosmiconfig.
I've been meaning to give jest
a whirl, would you mind that?
from cosmiconfig.
@JaKXz If you'd like to try, sure! It will be much more effort, though, since the syntax is more different from AVA's and the way of handling mocks will need to change. If that's the kind of challenge you seek, go for it.
from cosmiconfig.
Closing as stale, and probably out of scope for this package.
from cosmiconfig.
Related Issues (20)
- `explorer.search(...)` crashes with `{stopDir: undefined}` option HOT 2
- Node.js version breaking change HOT 2
- Why does cosmiconfig require Node version greater than 18.0.0? HOT 2
- Could not resolve module "node:os" from
- Regression in v8.3.x - missing json config file doesn't always return null HOT 9
- SyntaxError: Unexpected token '.' HOT 2
- Lerna-Lite project having an empty `.config.json` file gets picked up by cosmiconfig and is unexpected - behavior changed after 8.0 HOT 8
- Add link to Python port of Cosmiconfig HOT 2
- README doesn't mention .mjs files inside of a config directory HOT 2
- Error: EACCES: permission denied, open '/.config/puppeteerrc’ HOT 9
- Offer a "minimal" version with less dependencies
- Also find [`pnpm`] package.yaml/json5 properties HOT 1
- Module "typescript" possibly misplaced as a dev dependency HOT 1
- cosmiconfig requires at least version 4 of Node, please upgrade HOT 1
- Please release source code to npm if you release source map files HOT 1
- Question: latest v9 not mentioned in changelog and no github release exists HOT 2
- Meta config files are not looked in cwd anymore? (in v9 changelog but not in README HOT 6
- It says `.ts` configs are supported automatically, and also `.cjs` and `.mjs`, but why `.cts` and `.mts` are not supported?
- CJS configuration files in ESM projects do not freshly import
- Module not found errors when config imports from a file path
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cosmiconfig.