fitbit / enhanced-properties-loader Goto Github PK

View Code? Open in Web Editor NEW

8.0 2.0 3.0 584 KB

*.properties loader for webpack

Home Page: http://fitbit.github.io/enhanced-properties-loader

License: Apache License 2.0

JavaScript 100.00%

properties-loader webpack loader webpack-loader fitbit

enhanced-properties-loader's Introduction

enhanced-properties-loader

*.properties loader for webpack

Installation

npm install json-loader enhanced-properties-loader --save-dev

yarn add json-loader enhanced-properties-loader --dev

Usage

./index.properties

foo=bar
bar.baz=qux

./index.js

var properties = require('!json!enhanced-properties!./index.properties');

console.log(properties); // Object { foo: "bar", bar: { baz: "qux" } }

./webpack.config.js

module.exports = {
    module: {
        rules: [{
            test: /\.properties$/,
            loader: 'enhanced-properties-loader'
        }]
    }
};

enhanced-properties-loader's People

Contributors

Stargazers

Watchers

Forkers

mick-feller olivierceulemans pinkdiamond1

enhanced-properties-loader's Issues

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

Version 7.2.1 of babel-eslint just got published.

Branch	Build failing 🚨
Dependency	babel-eslint
Current Version	7.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-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

✅ dependency-ci Dependencies checked Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 6 commits .

3cda62e 7.2.1
5626de1 Remove left over eslint 2 estraverse code (#452)
b5fb53b Fix type param and interface declaration scoping (#449)
f1cee0f Remove lodash dependency (#450)
eb05812 Format non-regression errors for legibility (#451)
7972a05 Update README.md with codeFrame option (#448)

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 eslint-plugin-markdown is breaking the build 🚨

Version 1.0.0-beta.6 of eslint-plugin-markdown just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-markdown
Current Version	1.0.0-beta.4
Type	devDependency

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

As eslint-plugin-markdown 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

- ✅ **dependency-ci** Dependencies checked [Details](https://dependencyci.com/builds/202863),- ❌ **continuous-integration/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/mdreizin/enhanced-properties-loader/build/72),- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/Fitbit/enhanced-properties-loader/builds/227264351?utm_source=github_status&utm_medium=notification)

Release Notes

v1.0.0-beta.6

c5e9d67 Build: Explicitly specify package.json files (#67) (Brandon Mills)

Commits

The new version differs by 10 commits0.

65e296d 1.0.0-beta.6
07d179f Build: changelog update for 1.0.0-beta.6
c5e9d67 Build: Explicitly specify package.json files (#67)
8d5ae99 1.0.0-beta.5
91b3fa9 Build: changelog update for 1.0.0-beta.5
7bd0f6e Build: Install eslint-release (#66)
48122eb Build: Dogfood plugin without npm link (#65)
cc7deea Chore: Increase code coverage (#64)
29f2f05 Build: Use eslint-release (#63)
d2f2962 Upgrade: remark (#62)

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 codeclimate-test-reporter is breaking the build 🚨

Version 0.4.1 of codeclimate-test-reporter just got published.

Branch	Build failing 🚨
Dependency	codeclimate-test-reporter
Current Version	0.4.0
Type	devDependency

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

As codeclimate-test-reporter 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

✅ dependency-ci Dependencies checked Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 3 commits .

cb80deb Release 0.4.1
6a89360 Allow tests to run on Circle CI as well
d345e27 Add gitlab CI support

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 eslint is breaking the build 🚨

Version 3.16.0 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	3.15.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

✅ dependency-ci Dependencies checked Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v3.16.0

d89d0b4 Update: fix quotes false negative for string literals as template tags (#8107) (Teddy Katz)
21be366 Chore: Ensuring eslint:recommended rules are sorted. (#8106) (Kevin Partington)
360dbe4 Update: Improve error message when extend config missing (fixes #6115) (#8100) (alberto)
f62a724 Chore: use updated token iterator methods (#8103) (Kai Cataldo)
daf6f26 Fix: check output in RuleTester when errors is a number (fixes #7640) (#8097) (alberto)
cfb65c5 Update: make no-lone-blocks report blocks in switch cases (fixes #8047) (#8062) (Teddy Katz)
290fb1f Update: Add includeComments to getTokenByRangeStart (fixes #8068) (#8069) (Kai Cataldo)
ff066dc Chore: Incorrect source code test text (#8096) (Jack Ford)
14d146d Docs: Clarify --ext only works with directories (fixes #7939) (#8095) (alberto)
013a454 Docs: Add TSC meeting quorum requirement (#8086) (Kevin Partington)
7516303 Fix: sourceCode.getTokenAfter shouldn't skip tokens after comments (#8055) (Toru Nagashima)
c53e034 Fix: unicode-bom fixer insert BOM in appropriate location (fixes #8083) (#8084) (pantosha)
55ac302 Chore: fix the timing to define rules for tests (#8082) (Toru Nagashima)
c7e64f3 Upgrade: mock-fs (#8070) (Toru Nagashima)
acc3301 Update: handle uncommon linebreaks consistently in rules (fixes #7949) (#8049) (Teddy Katz)
591b74a Chore: enable operator-linebreak on ESLint codebase (#8064) (Teddy Katz)
6445d2a Docs: Add documentation for /* exported */ (fixes #7998) (#8065) (Lee Yi Min)
fcc38db Chore: simplify and improve performance for autofix (#8035) (Toru Nagashima)
b04fde7 Chore: improve performance of SourceCode constructor (#8054) (Teddy Katz)
90fd555 Update: improve null detection in eqeqeq for ES6 regexes (fixes #8020) (#8042) (Teddy Katz)
16248e2 Fix: no-extra-boolean-cast incorrect Boolean() autofixing (fixes #7977) (#8037) (Jonathan Wilsson)
834f45d Update: rewrite TokenStore (fixes #7810) (#7936) (Toru Nagashima)
329dcdc Chore: unify checks for statement list parents (#8048) (Teddy Katz)
c596690 Docs: Clarify generator-star-spacing config example (fixes #8027) (#8034) (Hòa Trần)
a11d4a6 Docs: fix a typo in shareable configs documentation (#8036) (Dan Homola)
1e3d4c6 Update: add fixer for no-unused-labels (#7841) (Teddy Katz)
f47fb98 Update: ensure semi-spacing checks import/export declarations (#8033) (Teddy Katz)
e228d56 Update: no-undefined handles properties/classes/modules (fixes #7964) (#7966) (Kevin Partington)
7bc92d9 Chore: fix invalid test cases (#8030) (Toru Nagashima)

Commits

The new version differs by 31 commits .

3c26a59 3.16.0
5bdb960 Build: package.json and changelog update for 3.16.0
d89d0b4 Update: fix quotes false negative for string literals as template tags (#8107)
21be366 Chore: Ensuring eslint:recommended rules are sorted. (#8106)
360dbe4 Update: Improve error message when extend config missing (fixes #6115) (#8100)
f62a724 Chore: use updated token iterator methods (#8103)
daf6f26 Fix: check output in RuleTester when errors is a number (fixes #7640) (#8097)
cfb65c5 Update: make no-lone-blocks report blocks in switch cases (fixes #8047) (#8062)
290fb1f Update: Add includeComments to getTokenByRangeStart (fixes #8068) (#8069)
ff066dc Chore: Incorrect source code test text (#8096)
14d146d Docs: Clarify --ext only works with directories (fixes #7939) (#8095)
013a454 Docs: Add TSC meeting quorum requirement (#8086)
7516303 Fix: sourceCode.getTokenAfter shouldn't skip tokens after comments (#8055)
c53e034 Fix: unicode-bom fixer insert BOM in appropriate location (fixes #8083) (#8084)
55ac302 Chore: fix the timing to define rules for tests (#8082)

There are 31 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 🌴

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from `15.13.11` to `15.13.12`.

🚨 View failing branch.

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/appveyor/branch: AppVeyor build failed (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v15.13.12

15.13.12 (2019-04-15)

Bug Fixes

package: update resolve-from to version 5.0.0 (6f3c21a)

Commits

The new version differs by 1 commits.

6f3c21a fix(package): update resolve-from to version 5.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 loader-utils is breaking the build 🚨

Version 0.2.16 of loader-utils just got published.

Branch	Build failing 🚨
Dependency	loader-utils
Current Version	0.2.15
Type	dependency

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

As loader-utils 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

✅ dependency-ci Dependencies checked Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded 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 .

4ea2dfb 0.2.16
e6dc9c1 allow query to be a object,

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 🌴

ERROR in Loader .....node_modules/enhanced-properties-loader/dist/index.js didn't return a function

var properties = require('!json!enhanced-properties-loader!./env.properties');
Working with react project.
fill error: ERROR in Loader /Users/kobi.or/Public/5d/client-react-2.0/node_modules/enhanced-properties-loader/dist/index.js didn't return a function
@ ./src/config/environment.js 3:17-77

and i using the last version.

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

Version 2.6.0 of jasmine just got published.

Branch	Build failing 🚨
Dependency	jasmine
Current Version	2.5.3
Type	devDependency

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

As jasmine 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

- ✅ **dependency-ci** Dependencies checked [Details](https://dependencyci.com/builds/199096),- ✅ **continuous-integration/appveyor/branch** AppVeyor build succeeded [Details](https://ci.appveyor.com/project/mdreizin/enhanced-properties-loader/build/68),- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/Fitbit/enhanced-properties-loader/builds/225379132)

Release Notes

2.6.0

Please see the release notes

Commits

The new version differs by 9 commits0.

94de6d5 Bump version to 2.6.0
6c3656f Merge branch 'lonelyelk-expose-reporters-management-api'
6cb6d27 Making jshint pass.
6f44d31 Expose closeReporters methos in the wrapper
023455c Try to detect a exit being called inside the suite
80e6b33 Merge branch 'add-config-option' of https://github.com/bcaudan/jasmine-npm into bcaudan-add-config-option
77acbb1 Merge branch 'bcaudan-reject-unknown-options'
88b838b Fix #53 - Reject unknown options
f527ab8 Fix #85 - Option to specify path to your jasmine.json

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 babel-plugin-transform-runtime is breaking the build 🚨

Version 6.23.0 of babel-plugin-transform-runtime just got published.

Branch	Build failing 🚨
Dependency	babel-plugin-transform-runtime
Current Version	6.22.0
Type	devDependency

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

As babel-plugin-transform-runtime 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

✅ dependency-ci Dependencies checked Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

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 eslint-plugin-babel is breaking the build 🚨

Version 4.1.0 of eslint-plugin-babel just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-babel
Current Version	4.0.1
Type	devDependency

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

As eslint-plugin-babel 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

✅ dependency-ci Dependencies checked Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v4.1.0

New

babel/semi: Includes class properties (🛠 ) #121

Thanks to @aaronjensen

Commits

The new version differs by 2 commits .

bde4f7a 4.1.0
14a367f Add babel semi (#121)

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-runtime is breaking the build 🚨

Version 6.23.0 of babel-runtime just got published.

Branch	Build failing 🚨
Dependency	babel-runtime
Current Version	6.22.0
Type	dependency

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

As babel-runtime 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

✅ dependency-ci Dependencies checked Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

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

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 🌴

fitbit / enhanced-properties-loader Goto Github PK

enhanced-properties-loader's Introduction

enhanced-properties-loader

Installation

Usage

enhanced-properties-loader's People

Contributors

Stargazers

Watchers

Forkers

enhanced-properties-loader's Issues

Version 7.2.1 of babel-eslint just got published.

Version 1.0.0-beta.6 of eslint-plugin-markdown just got published.

Version 0.4.1 of codeclimate-test-reporter just got published.

Version 3.16.0 of eslint just got published.

The devDependency semantic-release was updated from 15.13.11 to 15.13.12.

15.13.12 (2019-04-15)

Bug Fixes

Version 0.2.16 of loader-utils just got published.

Version 2.6.0 of jasmine just got published.

Version 6.23.0 of babel-plugin-transform-runtime just got published.

Version 4.1.0 of eslint-plugin-babel just got published.

New

Version 6.23.0 of babel-runtime just got published.

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

Recommend Projects

Recommend Topics

Recommend Org

The devDependency semantic-release was updated from `15.13.11` to `15.13.12`.