lucaperret / gaspard Goto Github PK
View Code? Open in Web Editor NEWLightweight DOM helpers without dependency
Home Page: https://lucaperret.github.io/gaspard
License: MIT License
gaspard's People
Contributors
![greenkeeper[bot] avatar](https://avatars.githubusercontent.com/in/505?v=4 "greenkeeper[bot]")
Stargazers
Watchers
Forkers
konstantina89fgaspard's Issues
An in-range update of babel7 is breaking the build 🚨
There have been updates to the babel7 monorepo:
-
- The
devDependency@babel/core was updated from7.1.0to7.1.1.
- The
- The
devDependency@babel/plugin-proposal-class-properties was updated from7.0.0to7.1.0. - The
devDependency@babel/plugin-proposal-decorators was updated from7.1.0to7.1.1. - The
devDependency@babel/plugin-proposal-function-sent was updated from7.0.0to7.1.0. - The
devDependency@babel/plugin-transform-modules-commonjs was updated from7.0.0to7.1.0. - The
devDependency@babel/plugin-transform-runtime was updated from7.0.0to7.1.0. - The
devDependency@babel/preset-env was updated from7.0.0to7.1.0.
This version is covered by your current version range and after updating it in your project the build failed.
This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.
babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
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 webpack is breaking the build 🚨
The devDependency webpack was updated from 4.26.1 to 4.27.0.
This version is covered by your current version range and after updating it in your project the build failed.
webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Release Notes for v4.27.0
Features
- When using functions as plugins they are now also called with the compiler as parameter
- This make it possible to use arrow functions as plugins
- splitChunks.maxSize now emits a warning when minSize > maxSize
- Loaders have now access to a
getResolvemethod to create their own resolver function with custom options
Bugfixes
- splitChunks.cacheGroups.xxx.enforce now behaves as documented and enforce chunk creation
- splitChunks.cacheGroups.xxx.enforce now no longer deletes minSize for maxSize
- fixes a bug where splitChunks cause cacheGroups to be incorrectly merged when using the same name
- now conditions are considered per cacheGroup
- the correct cache group comment is displayed in stats
- fixes a bug which causes providedExports not to be updated on rebuilds when using
export * from
Commits
The new version differs by 12 commits.
f47bf8b4.27.0a67ffcdMerge pull request #8452 from webpack/feature/resolveWithOptions96f625cMerge pull request #8457 from webpack/bugfix/rebuild-provided-exports56fecccconvert test case to normal function for node.js 6 support2f4296efix a bug which causes incorrect providedExports for cached modulesf944002Merge pull request #8451 from webpack/bugfix/split-chunks162da1cadd getResolve method to loader context3b46b48enforce doesn't affect minSize for maxSize72a8a1fMerge pull request #8440 from Connormiha/oprimize-chunk-can-be-integrated537d3e4Cache hasRunstime in chunke3e8a68Merge pull request #8405 from xiaoxiaojx/fix-function-plugin-apply70b9a1bfix parameter missing when plugin type is a funtion
See the full diff
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-plugin-jest is breaking the build 🚨
The devDependency eslint-plugin-jest was updated from 21.22.1 to 21.23.0.
This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Commits
The new version differs by 2 commits.
7515458feat(rules): require-tothrow-message (#160)a194da6chore: update lockfile with integrity field
See the full diff
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 webpack is breaking the build 🚨
Version 4.17.3 of webpack was just published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | webpack |
| Current Version | 4.17.2 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Release Notes
v4.17.3Bugfixes
- Fix exit code when multiple CLIs are installed
- No longer recommend installing webpack-command, but still support it when installed
Commits
The new version differs by 7 commits.
ee27d364.17.34430524Merge pull request #7966 from webpack/refactor-remove-webpack-command-from-clisb717aadShow only webpack-cli in the listc5eab67Merge pull request #8001 from webpack/bugfix/exit-code943aa6bFix exit code when multiple CLIs are installed691cc94Spelling898462drefactor: removewebpack-commandfrom CLIs
See the full diff
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 webpack-dev-server is breaking the build 🚨
The devDependency webpack-dev-server was updated from 3.7.1 to 3.7.2.
This version is covered by your current version range and after updating it in your project the build failed.
webpack-dev-server is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Commits
The new version differs by 21 commits.
26211fcchore(release): 3.7.224a348fchore(standard-version): add .versionrc to hide test's section (#2027)d26b444fix(client): add default fallback for client (#2015)84955f8docs(contribution): add CLA section (#1963)9707982chore(deps): update dependency webpack to ^4.34.0 (master) (#2032)b0cc63cchore(deps): update commitlint monorepo to v8 (master) (major) (#2033)7a5a00bchore(renovate): update config (#2030)3682bd7chore(deps): update dependency eslint-config-prettier to v5 (#2031)661f6a2chore(deps): update dependency lint-staged to ^8.2.1 (#2025)8481205docs: Fix CHANGELOG. (#2019)f611304test(e2e): make browser close before tests run (#2018)1ecc425chore(deps): update all patch dependencies (#2014)c982836docs: fix error message of clientLogLevel (#2021)303f4e9chore(deps): update dependency webpack-cli to ^3.3.4 (#2011)39b83c4test(provide-plugin): use port variable (#2008)
There are 21 commits in total.
See the full diff
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 coveralls is breaking the build 🚨
The devDependency coveralls was updated from 3.0.4 to 3.0.5.
This version is covered by your current version range and after updating it in your project the build failed.
coveralls is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Commits
The new version differs by 6 commits.
55fc4d8Merge branch 'master' of https://github.com/nickmerwin/node-coverallsb94fd9aversion bump0c147a8fix: vulnerabilities (#227)2c73fc8Bump lodash from 4.17.11 to 4.17.14 (#229)cf1921dUpdate configuration logic for Jenkins (#217)f0ddec5Add support for Azure Pipelines (#221)
See the full diff
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-plugin-import is breaking the build 🚨
The devDependency eslint-plugin-import was updated from 2.19.0 to 2.19.1.
This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
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 🌴
Get HTML Node
Hello,
I would like to create a PR to add a function that return html node
js
/**
* Return HTML node
* @return {element}
*/
export function getHtml () {
return document.getElementsByTagName('html')[0]
}
```
Very basic, i would like to know where should add the code ?
I was thinking of selectors, tellement if i'm wrong
Regards,
Arrowbaz
The automated release is failing 🚨
🚨 The automated release from the master branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.
Good luck with your project ✨
Your semantic-release bot 📦🚀
An in-range update of babel-loader is breaking the build 🚨
The devDependency babel-loader was updated from 8.0.2 to 8.0.3.
This version is covered by your current version range and after updating it in your project the build failed.
babel-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Release Notes for v8.0.3
Features
- #687 - Add
customizeoption
Bugs
- #685 - Also pass the caller option to loadPartialConfig
Docs
Internal
Some dev dependency updates and CI tweaks.
Commits
The new version differs by 12 commits.
800181b8.0.37d8500cAlso pass the caller option to loadPartialConfig (#685)a507914Expose the full loader options to all overrides hooks.ac0c869Tweak the customize implementation to be a bit more strict.9b70a02Add overrides optionc8d7a72Add .mjs to the examples (#683)4619993bable options link update (#681)8f240b4Use node 10 on appveyor7e4189eChange appveyor to use babel accounteeaee46Update devDeps to use most recent versions, and fix tests.3e5fb5echore(package): update lockfile2b8e479chore(package): update eslint-config-babel to version 8.0.0
See the full diff
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 🚨
The devDependency eslint was updated from 5.14.0 to 5.14.1.
This version is covered by your current version range and after updating it in your project the build failed.
eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Release Notes for v5.14.1
Commits
The new version differs by 3 commits.
b2e94d85.14.1ce129edBuild: changelog update for 5.14.11d6e639Fix: sort-keys throws Error at SpreadElement (fixes #11402) (#11403)
See the full diff
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 babel-eslint is breaking the build 🚨
The devDependency babel-eslint was updated from 10.0.0 to 10.0.1.
This version is covered by your current version range and after updating it in your project the build failed.
babel-eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Release Notes for v10.0.1
v10.0.1
- Reverting #584
The TypeAlias "conversion" to a function has issues. Sounds like we need to rethink the change, most likely we can just actually change the scoping rather than hardcode an AST change.
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-plugin-jest is breaking the build 🚨
The devDependency eslint-plugin-jest was updated from 22.1.0 to 22.1.1.
This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Commits
The new version differs by 1 commits.
73c9187fix: add guard for missing assertion invocation (#58)
See the full diff
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 semantic-release is breaking the build 🚨
The devDependency semantic-release was updated from 15.12.3 to 15.12.4.
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Release Notes for v15.12.4
15.12.4 (2018-11-30)
Bug Fixes
- remove unnecessary
branchparameter frompushfunction (ffe1062)
Commits
The new version differs by 1 commits.
ffe1062fix: remove unnecessarybranchparameter frompushfunction
See the full diff
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 webpack-cli is breaking the build 🚨
The devDependency webpack-cli was updated from 3.1.1 to 3.1.2.
This version is covered by your current version range and after updating it in your project the build failed.
webpack-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Commits
The new version differs by 17 commits.
795ac48v0.1.28225339chore: v.3.1.2>fb6945bMerge pull request #618 from webpack/fix/watch-info99f5a69Merge pull request #616 from rishabh3112/patch-44cba51dMerge pull request #615 from rishabh3112/patch-3d4e1614fix: replace test regexf3a225adocs(readme): update webpack-cli to webpack CLI9aed0dcfix(tapable): fix hook optionsdc4ded9docs(init): update headers747aef9docs(readme): change addons to scaffoldsf8187f1docs(readme): update links2ccf9a9docs(init): update init documentation3844671docs(readme): update README.md (#614)da05c2fdocs(readme): update Readme based on feedback93ebcc2chore(docs): update readme
There are 17 commits in total.
See the full diff
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 🌴
Adding methods to GaspardElements
Chaining is nice, GaspardElements' methods return this to have the ability to call other methods on this collection of elements.
We should add relevant methods to GaspardElements class.
Examples:
const elements = GaspardElements('#app')
elements.addClass('vue').css('background-color', 'green')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 - The new Node.js version is in-range for the engines in 1 of your
package.jsonfiles, so that was left alone
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.
engineswas only updated if it defined a single version, not a range..nvmrcwas updated to Node.js 10.travis.ymlwas only changed if there was a root-levelnode_jsthat didn’t already include Node.js 10, such asnodeorlts/*. 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 🌴
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.