Current Behavior

For every new project I start with TSDX, one of my first steps is to add stubs for static assets and stylesheets - as detailed on the Jest docs.

Desired Behavior

Add Jest file stubs in to the TSDX setup.

Suggested Solution

Following the Jest docs

// package.json
{
  "jest": {
    "m

I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [sta

It may be convenient to expose something to consumers that will make it easier to use Jest - something like the default babel options (presets, plugins, etc.) or a transform module (see something like https://github.com/ActuallyACat/jest-esm-transformer).

This makes using syntax like import/export much easier for folks who use this amazing library for bundling and Jest for tests.

Thank y

First of all, congrats on the great project!
I've started using it a couple of days ago but I've now started to bump onto some very big hurdles due to the fact that the Readme and all of the currently available documentation is scattered across several docs, the micro bundle project and so on.
I'm afraid this issue will end up being kind of redundant but I was unable to find anywhere else where

• Platform: MacOS
• Mercury Parser Version: master
• Node Version (if a Node bug): v11.1.0
• Browser Version (if a browser bug): n/a

Description

I have created a custom extractor for https://www.gruene.de/themen/arbeit which delivers the expected results for content and lead_image_url with the following specifications:

export const WwwGrueneDeExt

I just wanted to let you know: your documentation for v3 is broken.

https://v3--bili.netlify.com/

• Rollup Plugin Version: v5

Feature Use Case

When using the new babel .generated option, we lose the ability to deduplicate babel helpers. They're duplicated in each chunk. This really adds up, especially when compiling to es5. It would be useful to deduplicate these helpers, even when using .generated.

Feature Proposal

I created a babel + rollup plugin which adds imports for b

What problem does this feature solve?

I am creating a small package shipping some custom input fields for a project of ours. For templates I use pug. I decided to build it for production with rollup instead of webpack for a number of reasons. But it did not compile. For development (with webpack) I had no problem, the problem came from building with rollup.

After digging into the

Typescript 3 supports references:

• https://blogs.msdn.microsoft.com/typescript/2018/07/30/announcing-typescript-3-0/#project-references
• https://github.com/Soul-Master/typescript3-composite-project

Does this plugin respect references and include dependencies from depended upon packages in a mono repo?

My plugin config :

typescript({
      typescript: require('typescript'),
      exclude: ['**/*.stories.tsx', 'node_modules'],
    }),

My include/exclude in tsconfig

  "include": ["src/**/*", "typings/**/*"],
  "exclude": ["node_modules"]

Im seeing that the plugin is excluding the stories files from my output, however .d.ts files for them are

To me, the way @jwasilgeo is using loadModules with async/await here is much more readable. Do others agree? Now that async await is pretty mainstream (sorry IE11), I'm wondering if we should switch all our examples

rpm run e2e gives error on OSX.

 E/protractor - Could not find Angular on page http://127.0.0.1:57025/ : retries looking for angular exceeded
F
  App
    ✗ should have a title
      - Failed: Angular could not be found on the page http://127.0.0.1:57025/.If this is not an Angular application, you may need to turn off waiting for Angular.
                                Please see 
  

JSPM-mappings is not used by jest. Attempts to import front end dependencies in a test generates an error.

I am currently having a look at jest-jspm as a possible solution.

Feature request

Use case(s)

we are not updating tslint.json in existing project. Currently migrate script just echoes that nothing was updated, because it does no-op. This should be fixed/implemented. All we need to do is to find out how to properly merge .jsonc files ( json files with comments )