sivakumar-kailasam / ember-purify Goto Github PK

View Code? Open in Web Editor NEW

17.0 17.0 4.0 2.94 MB

Purify your html content before marking it safe

License: MIT License

JavaScript 73.19% HTML 19.71% CSS 7.10%

dompurify ember sanitization security xss

ember-purify's People

Contributors

Stargazers

Watchers

Forkers

kongregate ed-at-agari wozny1989 alyne

ember-purify's Issues

An in-range update of loader.js is breaking the build 🚨

Version 4.5.0 of loader.js just got published.

Branch	Build failing 🚨
Dependency	loader.js
Current Version	4.4.1
Type	devDependency

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

As loader.js 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 could not complete due to an error Details

Commits

The new version differs by 7 commits.

094e20b release v4.5.0 🎉
db2f6a6 Merge pull request #126 from ember-cli/moduleId
204838b rename mod.name => mod.id
4fa0fe0 add require.moduleId to allow a module to know its ID
f62bc54 Merge pull request #121 from ember-cli/define-exports
d963886 Update README.md
928e18f add define.exports

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 🌴

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.json files, 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.

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 loader.js is breaking the build 🚨

Version 4.2.0 of loader.js just got published.

Branch	Build failing 🚨
Dependency	loader.js
Current Version	4.1.0
Type	devDependency

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

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 is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 14 commits .

cc53069 release v4.2.0
1a453d3 Merge pull request #104 from trentmwillis/redefine
93478ef Improve redefinition scenarios
e289916 Fix test:dev command
287a487 Merge pull request #105 from trentmwillis/clarify
cda1c29 Clarify prime comment
562ecf1 Merge pull request #100 from jrowlingson/master
6a9b916 remove petal references
b609262 Merge pull request #95 from chadhietala/heimdall-instrumentation
c49296d Instrument with heimdall
453fe8c Merge pull request #97 from Turbo87/ci-deploy
37fef79 CI: Enable automatic NPM deployment for tags
c4f0755 Merge pull request #96 from chadhietala/dict-registry
8a34296 Use dict for registery and seen to avoid filling IC cache

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 ember-cli-babel is breaking the build 🚨

Version 6.2.0 of ember-cli-babel just got published.

Branch	Build failing 🚨
Dependency	ember-cli-babel
Current Version	6.1.0
Type	dependency

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

ember-cli-babel is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

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 15 commits.

1286e54 Revert "[FIXES #150] update babel-preset-env"
df2e98a release v6.2.0 🎉
346b53c [FIXES #150] update babel-preset-env
603667a Merge pull request #148 from babel/node-8
79a33cf allow node 8 to fail until ember-cli is updated
5b52b66 lock to older version of preset-env (before the breaking change)
fb07e99 skip failed test
86260f4 skip test that is failing because babel-preset-env changed it API (will fix later)
6eb7285 [BUGFIX #147] add node 8 support
65038c7 Merge pull request #144 from babel/update
b8e1107 upgrade all the deps
aca5787 Merge pull request #139 from rwjblue/update-readme
718e419 Specifically call out the @glimmer/env import path.
7567ada Merge pull request #138 from babel/Turbo87-patch-1
ffb7850 README: Add missing return type

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 ember-cli-htmlbars is breaking the build 🚨

Version 1.3.1 of ember-cli-htmlbars just got published.

Branch	Build failing 🚨
Dependency	ember-cli-htmlbars
Current Version	1.3.0
Type	devDependency

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

As ember-cli-htmlbars 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/appveyor/branch Waiting for AppVeyor build to complete Details,- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 4 commits0.

b46eb48 v1.3.1
f0c03ec Merge pull request #109 from ember-cli/use-non-deprecated-version-checker-api
faf7f25 Add yarn.lock.
1b27f67 Update ember-cli-version-checker use to avoid deprecated APIs.

false

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 ember-disable-prototype-extensions is breaking the build 🚨

Version 1.1.2 of ember-disable-prototype-extensions just got published.

Branch	Build failing 🚨
Dependency	ember-disable-prototype-extensions
Current Version	1.1.0
Type	devDependency

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

As ember-disable-prototype-extensions 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 could not complete due to an error Details

Commits

The new version differs by 7 commits.

11e41e5 release v1.1.2 🎉
7cbd03c release v1.1.1 🎉
e345d11 Merge pull request #10 from ember-cli/upgrade
37248ad add travis badge
2374b13 add appveyor
07de228 upgrade
599396e Update README.md

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 🌴

ember-config-service dependency

It looks like in the 5.0 release, a dependency to the ember-config-service addon was introduced, but is not listed as a dependency in package.json.

I found it because our test suite started failing, saying it couldn't inject service:config, and looking at the commits I was able to figure it out.

It is listed as a devDependency for the dummy app, which is why the test suite here is still passing.

I'm admittedly not very knowledgable about addons or how they interact with each other, if we move ember-config-service from devDependencies to dependencies, will that fix it?

In the meantime, I've installed the addon in our app and that fixed the error for us.

sivakumar-kailasam / ember-purify Goto Github PK

ember-purify's People

Contributors

Stargazers

Watchers

Forkers

ember-purify's Issues

Version 4.5.0 of loader.js just got published.

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

Version 4.2.0 of loader.js just got published.

Version 6.2.0 of ember-cli-babel just got published.

Version 1.3.1 of ember-cli-htmlbars just got published.

Version 1.1.2 of ember-disable-prototype-extensions just got published.

Recommend Projects

Recommend Topics

Recommend Org