comandeer / rollup-plugin-mockr Goto Github PK

View Code? Open in Web Editor NEW

1.0 2.0 0.0 67 KB

License: MIT License

JavaScript 100.00%

rollup-plugin mocker rollup-plugin-mockr

rollup-plugin-mockr's Introduction

rollup-plugin-mockr

Allows mocking ES6 modules for tests. Heavily inspired by rollup-plugin-alias.

Installation

npm install rollup-plugin-mockr [--save-dev]

Usage

import { rollup } from 'rollup';
import mockr from 'rollup-plugin-mockr';

rollup( {
	entry: './src/index.js',
	plugins: [
		mockr( {
			'./src/index.js': {
				exampleLib: 'path/to/localMock'
			}
		} )
	]
} );

You can also specify file extension for ES6 modules:

rollup( {
	entry: './src/index.js',
	plugins: [
		mockr( {
			modules: {
				'./src/index.js': {
					exampleLib: 'path/to/localMock'
				}
			},
			fileExtension: 'jsm'
		} )
	]
} );

You can also specify more than one entry point (added with karma-rollup-preprocessor in mind; unfortunately it doesn't work with rollup-plugin-multi-entry… yet).

rollup( {
	entry: './src/index.js',
	plugins: [
		mockr( {
			'./src/index.js': {
				exampleLib: 'path/to/localMock'
			},
			'./src/index2.js': {
				someOtherLib: 'path/to/localMock2'
			}
		} )
	]
} );

License

See LICENSE file for details.

rollup-plugin-mockr's People

Contributors

Stargazers

Watchers

rollup-plugin-mockr's Issues

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

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.56.4 of rollup was just published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.56.3
Type	devDependency

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

rollup 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 38 commits.

018bcd2 0.56.4
a7627e3 Merge branch 'release-0.56.4'
58a6da4 Reset git on postcommit to fix a webstorm issue
65dd2d1 Merge branch 'asmockler-prettier' into release-0.56.4
77079db Merge branch 'system-form' into release-0.56.4
53003b8 Merge branch 'lamby-reproducible-build' into release-0.56.4
9291989 Merge branch 'reexport-tracing' into release-0.56.4
c3da6aa Merge branch 'chunk-import-variable-deduping' into release-0.56.4
e932f95 Merge branch 'throw-on-warnings' into release-0.56.4
3f74e82 Merge branch 'system-default-formatting' into release-0.56.4
8c56d63 Merge branch 'adrianheine-sourcemap' into release-0.56.4
dfc3280 0.56.3
8865311 Make sure tests are only removed if they contain at most an "_actual" directory
fa7a618 Automatically remove directories of missing tests instead of throwing an error
ccd9d23 getModuleDeclarations refactoring

There are 38 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 mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.3.0
Type	devDependency

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

As mocha 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 failed Details

Release Notes

v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

allowUncaught added to commandline as --allow-uncaught (and bugfixed)
warning-related Node flags

🎉 Enhancements

#2793, #2697: add --allowUncaught to Node.js (@lrowe)
#2733: Add --no-warnings and --trace-warnings flags (@sonicdoe)

🐛 Fixes

#2793, #2697: fix broken allowUncaught (@lrowe)

🔩 Other

#2778: Add license report and scan status (@xizhao)
#2794: no special case for macOS running Karma locally (@boneskull)
#2795: reverts use of semistandard directly ([#2648]) (@boneskull)

Commits

The new version differs by 9 commits0.

7554b31 Add Changelog for v3.4.0
9f7f7ed Add --trace-warnings flag
92561c8 Add --no-warnings flag
ceee976 lint test/integration/fixtures/simple-reporter.js
dcfc094 Revert "use semistandard directly"
93392dd no special case for macOS running Karma locally
4d1d91d --allow-uncaught cli option
fb1e083 fix allowUncaught in browser
4ed3fc5 Add license report and scan status

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 🌴

Ability to match more than one module

Due to #29, there should be introduced the way to match more than one module with one rule. Preferably it should be done using the regexes.

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 🌴

The plugin should strictly match the modules

Having the JS module with imports like:

import A from './Test';
import B from './TestNotToMock';

and passing it to the mockr with the options to mock the Test modules we'll end with

import A from './Mockd';
import B from './MockdNotToMock';

The mockr should not perform partial matching, but the full matching.

comandeer / rollup-plugin-mockr Goto Github PK

rollup-plugin-mockr's Introduction

rollup-plugin-mockr

Installation

Usage

License

rollup-plugin-mockr's People

Contributors

Stargazers

Watchers

rollup-plugin-mockr's Issues

Version 0.56.4 of rollup was just published.

Version 3.4.0 of mocha just got published.

🎉 Enhancements

🐛 Fixes

🔩 Other

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

Recommend Projects

Recommend Topics

Recommend Org