🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

• Commitzen
• Conventional-changelog
• Lerna-semantic-release

Add blueprints files for the jade (and handlebar template) + e2e test

• Use async methods only (ie from fs/fs-extra)
• Compile could be written without async.waterfall as the 3 compilations could perhaps be run in parallel

• use lerna publish -m to adhere to commitizen

• use --conventional-commits when publishing

• address and update the following related deprecations:

• npm WARN deprecated [email protected]: Check out CommitLint which provides the same functionality with a more user-focused experience.

• npm WARN deprecated [email protected]: Please update conventional-changelog to >1.0.0. If you are running the cli, use conventional-changelog-cli

Template could expose an alternative url (for the externals). ie: a normal url for production and a devUrl for dev (think of ../library.min.js and ../library.js). For example the react non minified/production version of the library support extensive error/debugging

We're opening this issue to inform you about problems with your dependencies.io configuration or build failures.

We'll add a comment here when we see problems. You can close this issue when
you have things resolved -- we'll open it back up if we detect new problems.

Helpful links:

• dependencies.io/docs
• https://app.dependencies.io/

Note: To help keep your repo as clean as possible, this is the only issue
that we're going to open and comment on. Feel free to delete the comments
that are made as you resolve them, if you want to keep this issue short and tidy.

infinite-loop-loader produces invalid Javascript when transforming if, else and while in shorthand syntax.

For example, try using infinite-loop-loader with this:

if (false) while (i++ < 10) { console.log('This is ok'); }
else while (i++ < 10) { console.log('This else breaks things'); }

The output from Webpack:

ERROR in ./index.js
Module parse failed: /Users/davidfutcher/code/prefunnel/infinite-loop-loader-example/node_modules/infinite-loop-loader/index.js??ref--0!/Users/davidfutcher/code/prefunnel/infinite-loop-loader-example/index.js Unexpected token (10:0)
You may need an appropriate loader to handle this file type.
|       __ITER--;
|        console.log('This is ok'); }
| else
|       var __ITER = 1000000000;
|       while (i++ < 10) { if (__ITER <= 0) {

Looks like the loader assumes it's adding code into a bracketed block, which is not necessarily true (there are obvious missing brackets between the else and the var). This syntax (for better or worse!) exists in the wild - it was found when trying to import d3-time into an OC - see https://github.com/d3/d3-time/blob/master/src/interval.js#L43.

Moved from nickbalestra/infinite-loop-loader#3

Info:
So that when the loader is in a chain of loaders, the source map properly maps the transformation.

To create sourcemaps, this project seems to be pretty good: https://github.com/mozilla/source-map#generating-a-source-map

Here an example of how to add sourcemaps to falafel (using your suggest source-map) : alltom/node-falafel-map@5b20ef2

Due to the many shared packages that both legacy templates (jade and handlebars) rely on, Is advised to merge them both together and rename this repo into base-templates so that development on each template together with work needed on any shared package (webpack configurator, infinite-loop-loader,...) will be more accessible and publishing will require way less efforts. Nonetheless we already have a lerna structure on both, so the transaction will be seamless

We're opening this issue to inform you about problems with your dependencies.io configuration or build failures.

We'll add a comment here when we see problems. You can close this issue when
you have things resolved -- we'll open it back up if we detect new problems.

Helpful links:

• dependencies.io/docs
• https://app.dependencies.io/

Note: To help keep your repo as clean as possible, this is the only issue
that we're going to open and comment on. Feel free to delete the comments
that are made as you resolve them, if you want to keep this issue short and tidy.

Could be interesting to investigate supporting css-modules for the handlebars and jade templates

• few references for handlebars
  • https://www.npmjs.com/package/interpolate-html-css-modules-webpack-plugin
  • https://github.com/lucasconstantino/handlebars-css-modules-sample

Everything within the to-be-published directory being worked on #15 should be moved into own package.

Once #16 and #17 has been done, move in the infinite-loop-loader package as well

Once oc-template-react become stable,
bring into base-template packages the needec changes so that they will support building similar templates as well.

We think it may be related to the following PR:
https://github.com/opencomponents/base-templates/pull/372/files

However we are now receiving the following message when booting up OC when using the oc-template-es6-compiler with the following error message:

Error: Cannot find module './lib/oc-webpack'
at Function.Module._resolveFilename (module.js:548:15)
at Function.Module._load (module.js:475:25)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)

I can look at this, but will need some time.

If you're seeing a similar issue, fixing oc-template-es6-compiler to 1.1.3 fixes the issue for now.

Add lerna-changelog so that we can get changelog automatically upon publishing

Move tests within each package and use lerna + stage-lint + jest to orchestrate to running all related tests

https://yarnpkg.com/blog/2017/08/02/introducing-workspaces/