-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Eslint/Updates (and drop Gulp) #131
base: master
Are you sure you want to change the base?
Conversation
- Babel: Switch to use "json" extension - Maintenance: Add `.editorconfig` - Travis: Add Node 10 and 12 - package.json: Add `bugs` - npm: Add npmrc to avoid `package-lock.json`
- Linting: Remove deprecated `ecmaFeatures` from config
…const`/`let` closer to necessary scope
- npm: Switch to non-deprecated babel/preset-env and to Babel 7 - npm: Update deps. (esrecurse, estraverse (major bump)) and devDeps. - Testing: Fix esprima imports - Testing: Add nyc - Testing: Update export tests to avoid error with exported variable not being defined
- Testing: Fix `es6-destructuring-assignments.js` check of rest element per updated Esprima
- npm: Remove gulpfile (including its bump functionality which has not currently been replaced)
…res only needed in earlier versions)
- Build enhancement: Provide ESM build - npm: Point to browser and ESM builds in package.json fields
Can't we replace the bump script with https://docs.npmjs.com/cli-commands/version.html? |
Yes, I think so, depending on how you want it configured I guess. Do you want npm scripts for each bump type or do you just want to use these on your own? I have a feeling this is more the kind of thing you might want to tweak to your liking. I think the only thing of probable relevance from the Gulpfile removal is just that the commit message had been "Bumps package version" if you wish to keep it consistent. |
Yeah I don't really care about commit message consistency.
That seems a bit unnecessary. |
Ok, I guess that's all you need from me for now then? Btw, off topic, and no worries if there is no interest, but wanted to offer https://github.com/brettz9/es-file-traverse for your consideration for inclusion on estools, as I think it fills a basic need and should be relevant to the organization. |
- npm: Use rollup/plugin-babel over deprecated rollup-plugin-babel
Think you can find time to review? |
A few disclaimers:
I'm also not fully sure whether myI've added Rollupbrowserify
script replacement for the gulp file works as intended, but I've set it asstandalone
so it could be used as is (if you are ok with Rollup, I could add that in its place, getting an ESM distribution in the process as well).bump
functionality from the gulp file (the only remaining item which was not ported). I see there is a CLI option if you wanted me to add that: https://www.npmjs.com/package/npm-bumpecmaFeatures
from configprefer-const
) and manual fixes per config (e.g.,prefer-destructuring
) and movingconst
/let
closer to necessary scopebrowserify
scriptbugs
andkeywords
; use package.json linter-recognizedauthor
/contributors
overmaintainers
.npmrc
to avoidpackage-lock.json
@babel/preset-env
and to Babel 7.editorconfig
es6-destructuring-assignments.js
check of rest element per updated Esprima