Since Babel 7 the Babel team switched to [scoped packages][1], so you now have to use `@babel/core` instead of `babel-core`.  
But in essence, `@babel/core` is just a newer version of `babel-core`.

This is done to make a better distinction which  packages are official and which are third-party.


  [1]: https://babeljs.io/docs/en/next/v7-migration#scoped-packages

Inspired by question [Why is the Java 11 base Docker image so large? (openjdk:11-jre-slim)][1] I found that this topic in Java world is still not settled.

As for `07 Dec 2018` there are common issues/pitfalls (discussed in the ticket above):

  - JRE is not distributed as a separate &quot;package&quot;. Modules from JDK should be used instead

  - [Oracle OpenJDK 11][2] doesn&#39;t support [Linux Alpine][3], so _lightweight_ images can&#39;t be easily created

    - In the same time current stable Debian versions still doesn&#39;t have [Java 11 packages][4] ([Ubuntu has Java 10 installed][5] under openjdk-11 packages), that&#39;s why unstable sid versions are used for base docker images

  - currently available Oracle openjdk-11 images build unstripped `libjvm.so` module, which has hundreds megabyte and must be stripped separately:
  
    - [jlink runtime image size (specifically libjvm.so) created from openjdk is huge. Expected it to be much smaller.][6]
    - Solution: https://github.com/docker-library/openjdk/issues/217#issuecomment-436079779

As a result of these issues even _slim_ Oracle Java 11 base images are quite heavy and considered to be unstable: https://hub.docker.com/_/openjdk/

So the question is: 

**what are _optimized_ or _recommended_ ways to build and deliver Java 11 applications as docker images**?


  [1]: https://stackoverflow.com/questions/53375613/
  [2]: https://jdk.java.net/11/
  [3]: https://openjdk.java.net/projects/portola/
  [4]: https://packages.debian.org/stable/java/
  [5]: https://packages.ubuntu.com/bionic/java/
  [6]: https://github.com/docker-library/openjdk/issues/217

Java 11 application as lightweight docker image

I have added **AppBar** in my flutter application. My screen already have a background image, where i don&#39;t want to set appBar color or don&#39;t want set separate background image to appBar. 

I want show same screen background image to appBar also.

I already tried by setting appBar color as transparent but it shows color like gray. 

**Example code:**

    appBar: new AppBar(
            centerTitle: true,
    //        backgroundColor: Color(0xFF0077ED),
            elevation: 0.0,
            title: new Text(
                &quot;DASHBOARD&quot;,
                style: const TextStyle(
                    color:  const Color(0xffffffff),
                    fontWeight: FontWeight.w500,
                    fontFamily: &quot;Roboto&quot;,
                    fontStyle:  FontStyle.normal,
                    fontSize: 19.0
                )),
          )


[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/Rt8uv.png

Make AppBar transparent and show background image which is set to whole screen

What is the difference between
&lt;a href=&quot;https://www.npmjs.com/package/babel-core&quot;&gt;babel-core&lt;/a&gt;  and &lt;a href=&quot;https://www.npmjs.com/package/@babel/core&quot;&gt;@babel/core&lt;/a&gt; ?

Are they the same thing but different versions? If not so, when do you use one and when do you use the other?

Thank you.


What is the difference between babel-core and @babel/core?

What is the difference between
<a href="<a href=" https:="" www.npmjs.com="" package="" babel-core&#x26;quot;&#x26;gt;babel-core&#x26;lt;="" a&#x22;="">https://www.npmjs.com/package/babel-core">babel-core&#x3C;/a</a>> and <a href="<a href=" https:="" www.npmjs.com="" package="" @babel="" core&#x26;quot;&#x26;gt;@babel="" core&#x26;lt;="" a&#x22;="">https://www.npmjs.com/package/@babel/core">@babel/core&#x3C;/a</a>> ?
Are they the same thing but different versions? If not so, when do you use one and when do you use the other?
Thank you.

I have an application that is a node backend and a react frontend.

I get the following error when i try to build/run my node application.

Node: `v10.13.0`


**Error:**

&gt; dist/index.js:314
&gt;       regeneratorRuntime.mark(function _callee(productId) {
&gt;       ^
&gt; 
&gt; ReferenceError: regeneratorRuntime is not defined


**.babelrc**

    {
        &quot;presets&quot;: [    [
            &quot;@babel/preset-env&quot;, {
              &quot;targets&quot;: {
                &quot;node&quot;: &quot;current&quot;
              },
            }
          ], &quot;@babel/preset-react&quot;],
        &quot;plugins&quot;: [
            &quot;@babel/plugin-proposal-class-properties&quot;
        ]
    }

**webpack.config.js**


    {
            mode: &quot;development&quot;,
            entry: &quot;./src/index.js&quot;,
            target: &quot;node&quot;,
            externals: [nodeExternals()], // in order to ignore all modules in node_modules folder
            stats: {
                colors: true
            },
            devtool: &quot;source-map&quot;,
    
            output: {
                path: path.resolve(__dirname, &quot;dist&quot;),
                filename: &quot;index.js&quot;,
                sourceMapFilename: &quot;index.js.map&quot;
            },
            module: {
                rules: [
                    {
                        enforce: &quot;pre&quot;,
                        test: /\.js$/,
                        exclude: /node_modules/,
                        loader: &quot;eslint-loader&quot;,
                    },
                    {
                        test: /\.m?js$/,
                        exclude: /(node_modules|bower_components)/,
                        use: {
                            loader: &quot;babel-loader&quot;,
                            options: {
                                presets: [&quot;@babel/preset-env&quot;]
                            }
                        }
                    }
                ],
            },
            node: {
                __dirname: false,
                __filename: false,
            },
    
            &quot;plugins&quot;: [
                new CleanWebpackPlugin(),
                new WebpackShellPlugin({
                    onBuildStart: [],
                    onBuildEnd: [&quot;nodemon dist/index.js&quot;]
                }),
     
            ]
    
        },


**package.json**

     &quot;dependencies&quot;: {
        &quot;connect&quot;: &quot;^3.6.6&quot;,
        &quot;cors&quot;: &quot;^2.8.5&quot;,
        &quot;dotenv&quot;: &quot;^6.1.0&quot;,
        &quot;express&quot;: &quot;^4.16.4&quot;,
        &quot;hellojs&quot;: &quot;^1.17.1&quot;,
        &quot;i18n-iso-countries&quot;: &quot;^3.7.8&quot;,
        &quot;morgan&quot;: &quot;^1.9.1&quot;,
        &quot;react&quot;: &quot;^16.6.3&quot;,
        &quot;react-dom&quot;: &quot;^16.6.3&quot;,
        &quot;request&quot;: &quot;^2.88.0&quot;,
        &quot;request-promise-native&quot;: &quot;^1.0.5&quot;,
        &quot;serve-static&quot;: &quot;^1.13.2&quot;,
        &quot;vhost&quot;: &quot;^3.0.2&quot;
      },
      &quot;devDependencies&quot;: {
        &quot;@babel/cli&quot;: &quot;^7.1.5&quot;,
        &quot;@babel/core&quot;: &quot;^7.1.6&quot;,
        &quot;@babel/plugin-proposal-class-properties&quot;: &quot;^7.1.0&quot;,
        &quot;@babel/preset-env&quot;: &quot;^7.1.6&quot;,
        &quot;@babel/preset-react&quot;: &quot;^7.0.0&quot;,
        &quot;babel-eslint&quot;: &quot;^10.0.1&quot;,
        &quot;babel-loader&quot;: &quot;^8.0.4&quot;,
        &quot;clean-webpack-plugin&quot;: &quot;^1.0.0&quot;,
        &quot;copy-webpack-plugin&quot;: &quot;^4.6.0&quot;,
        &quot;css-loader&quot;: &quot;^1.0.1&quot;,
        &quot;eslint&quot;: &quot;^5.9.0&quot;,
        &quot;eslint-config-google&quot;: &quot;^0.10.0&quot;,
        &quot;eslint-loader&quot;: &quot;^2.1.1&quot;,
        &quot;eslint-plugin-react&quot;: &quot;^7.11.1&quot;,
        &quot;extract-loader&quot;: &quot;^3.0.0&quot;,
        &quot;file-loader&quot;: &quot;^2.0.0&quot;,
        &quot;node-sass&quot;: &quot;^4.10.0&quot;,
        &quot;sass-loader&quot;: &quot;^7.1.0&quot;,
        &quot;style-loader&quot;: &quot;^0.23.1&quot;,
        &quot;webpack&quot;: &quot;^4.26.0&quot;,
        &quot;webpack-cli&quot;: &quot;^3.1.2&quot;,
        &quot;webpack-node-externals&quot;: &quot;^1.7.2&quot;,
        &quot;webpack-shell-plugin&quot;: &quot;^0.5.0&quot;
      }




Babel 7 - ReferenceError: regeneratorRuntime is not defined

I try to config a environment to develop javascript with babel and webpack.

But I don&#39;t understand babel configuration about `presets`.

In [Usage Guide](https://babeljs.io/docs/en/usage), we can see that presets with `&quot;@babel/env&quot;`.

But other places in document, I cannot see such a configuration more, instead of `&quot;@babel/preset-env&quot;`. for example here &lt;https://babeljs.io/docs/en/babel-preset-env&gt;

I can not find out the difference between `&quot;@babel/env&quot;` and `&quot;@babel/preset-env&quot;` everywhere with my poor English, I do really read document again and again, without luck.

Maybe they are same?

Btw, targets sets seems not work, remove targets also can run normally in ie9+(or what&#39;s it default targets), if I wish my es6 script can be transformed to compatibility ie8, thus it not most important.

here is my project [sdk-dev-env](https://github.com/whidy/sdk-dev-env/tree/for-es6-without-babel/polyfill)

```
// https://babeljs.io/docs/en/configuration
const presets = [
  [
    &#39;@babel/env&#39;,
    {
      // https://babeljs.io/docs/en/babel-preset-env#targets
      // TODO: how to compatibilite with ie 8
      targets: {
        ie: &#39;8&#39;,
        edge: &#39;17&#39;,
        firefox: &#39;60&#39;,
        chrome: &#39;67&#39;,
        safari: &#39;11.1&#39;
        /**
         * you can also set browsers in package.json
         * &quot;browserslist&quot;: [&quot;last 3 versions&quot;]
         * relative links:
         * https://github.com/browserslist/browserslist
         */
      },
      corejs: &#39;3&#39;,
      // corejs: { version: 3, proposals: true },
      /**
       * https://babeljs.io/docs/en/usage#polyfill
       * https://github.com/zloirock/core-js#babelpreset-env
       * &quot;usage&quot; will practically apply the last optimization mentioned above where you only include the polyfills you need
       */
      useBuiltIns: &#39;usage&#39;
    }
  ]
]
const plugins = []

if (process.env[&#39;ENV&#39;] === &#39;prod&#39;) {
  // plugins.push(...);
}
module.exports = { presets, plugins }
```

I hope to know they are same or not, if not, what different.

And the best way to use babeljs 7.4 with core-js 3

confused with babel preset configs between @babel/env and @babel/preset-env

I have a React application (not using Create React App) built using TypeScript, Jest, Webpack, and Babel. When trying to run `yarn jest`, I get the following error:

![jest error](https://i.imgur.com/bkIisp8.png)

I have tried removing all packages and re-adding them.  It does not resolve this.  I have looked at similar questions and documentation and I am still misunderstanding something. I went so far as to follow another guide for setting up this environment from scratch and still received this issue with my code.

Dependencies include...
```
&quot;dependencies&quot;: {
  &quot;@babel/plugin-transform-runtime&quot;: &quot;^7.6.2&quot;,
  &quot;@babel/polyfill&quot;: &quot;^7.6.0&quot;,
  &quot;babel-jest&quot;: &quot;^24.9.0&quot;,
  &quot;react&quot;: &quot;^16.8.6&quot;,
  &quot;react-dom&quot;: &quot;^16.8.6&quot;,
  &quot;react-test-renderer&quot;: &quot;^16.11.0&quot;,
  &quot;source-map-loader&quot;: &quot;^0.2.4&quot;
},
&quot;devDependencies&quot;: {
  &quot;@babel/core&quot;: &quot;^7.6.0&quot;,
  &quot;@babel/preset-env&quot;: &quot;^7.6.0&quot;,
  &quot;@babel/preset-react&quot;: &quot;^7.0.0&quot;,
  &quot;@types/enzyme&quot;: &quot;^3.9.2&quot;,
  &quot;@types/enzyme-adapter-react-16&quot;: &quot;^1.0.5&quot;,
  &quot;@types/jest&quot;: &quot;^24.0.13&quot;,
```

The component&#39;s import lines...
```
import * as React from &quot;react&quot;;
import { BrowserRouter as Router, Route, Switch } from &quot;react-router-dom&quot;;
import HomePage from &quot;./components/pages&quot;;
import {
  Footer,
  Header,
  Navigation,
} from &quot;./components/shared&quot;;
```

The test file....
```
import * as React from &quot;react&quot;;
import * as renderer from &quot;react-test-renderer&quot;;
import App from &quot;../App&quot;;

it(&quot;Renders the Footer correctly&quot;, () =&gt; {
  const tree = renderer
    .create(&lt;App /&gt;)
    .toJSON();
  expect(tree).toMatchSnapshot();
});
```

I expected to be able to use named imports in my components without my tests blowing up.  It appears to fix the issue if I only use default imports through my solution, but I would prefer to not go that route.

How to resolve &quot;Cannot use import statement outside a module&quot; in jest

I was learning Babel and wanted to learn how to configure Babel. I found two ways to configure Babel: by creating babel.config.js and .babelrc file. Under what circumstances should we prefer one config file over the other?

When to use babel.config.js and .babelrc

I have been encountering this error on every single new Next.js project that I create. The page can be compiled without any problem, it just keeps on showing as error on the first line in every js file.

Parsing error: Cannot find module &#39;next/babel&#39;
Require stack:
- D:\app\next_app\ratu-seo\node_modules\next\dist\compiled\babel\bundle.js
- D:\app\next_app\ratu-seo\node_modules\next\dist\compiled\babel\eslint-parser.js
- D:\app\next_app\ratu-seo\node_modules\eslint-config-next\parser.js
- D:\app\next_app\ratu-seo\node_modules\@eslint\eslintrc\lib\config-array-factory.js
- D:\app\next_app\ratu-seo\node_modules\@eslint\eslintrc\lib\index.js
- D:\app\next_app\ratu-seo\node_modules\eslint\lib\cli-engine\cli-engine.js
- D:\app\next_app\ratu-seo\node_modules\eslint\lib\cli-engine\index.js
- D:\app\next_app\ratu-seo\node_modules\eslint\lib\api.js
- c:\Users\Admin\.vscode\extensions\dbaeumer.vscode-eslint-2.1.23\server\out\eslintServer.js

Parsing error : Cannot find module &#39;next/babel&#39;

I couldn&#39;t get rid of this `SyntaxError: Cannot use import statement outside a module` error no matter what I have tried and it got so frustrating. Is there anybody out here solved this issue? I have read a million stackoverflow and github issue threads. No clear solutions.

This is a React, Typescript, Webpack project. I am trying to test a module. But Jest won&#39;t transform the **module to plain javascript** somehow.

## The error I get is

```
/Users/me/dev/Project/project/node_modules/variables/src/variables.js:12
    import &#39;./main.js&#39;;
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      17 | 
      18 | */
    &gt; 19 | import { GlobalVars } from &#39;variables&#39;
         | ^
      20 | 
      21 | export const Vars = new GlobalVars()
      22 | 
```

## What I have tried to solve this (and didn&#39;t work):

- Using `env` setup in `babel.config`: `env.test.preset: [&#39;@babel/plugin-transform-modules-commonjs&#39;]`

- modifying `transform` setup in Jest configuration as `&#39;^.+\\.jsx?$&#39;: &#39;babel-jest&#39;, &#39;^.+\\.tsx?$&#39;: &#39;ts-jest&#39;` and all other possibilities around this.

- In Jest configuration, `testPathIgnorePatterns`, `transformIgnorePatterns`

- Using  `.babel.config.js` instead of `.babelrc.js`

...and more.

## I have this setup:

**package.json**
```json
  &quot;jest&quot;: {
    &quot;preset&quot;: &quot;ts-jest&quot;,
    &quot;testEnvironment&quot;: &quot;node&quot;
  }
```

**.babelrc.js**

```javascript
module.exports = {
  presets: [
    [&#39;@babel/preset-env&#39;, { targets: { node: &#39;current&#39; } }],
    &#39;@babel/preset-react&#39;,
    &#39;@babel/preset-typescript&#39;,
  ],
  plugins: [
    &#39;@babel/plugin-transform-runtime&#39;,
    &#39;@babel/proposal-class-properties&#39;,
    &#39;@babel/transform-regenerator&#39;,
    &#39;@babel/plugin-transform-template-literals&#39;,
    &#39;react-hot-loader/babel&#39;,
  ],
}
```

**variables.ts**

```javascript
import { GlobalVars } from &#39;variables&#39;

export const Vars = new GlobalVars()
```

**variables.spec.ts**

```javascript
import { Vars } from &#39;./variables.ts&#39;

describe(&#39;Test The Package&#39;, () =&gt; {
  it(&#39;Should accept new variables&#39;, () =&gt; {
    Vars.newVariable = &#39;new variable&#39;
    expect(Vars.newVariable).toEqual(&#39;new variable&#39;)
  })
})

```

Any idea on how to resolve this problem?

Content Type	Original Author	Original Content on Stackoverflow
Question	YulePale	View Question on Stackoverflow
Solution 1 - Babeljs	MichaelDeBoey	View Answer on Stackoverflow

What is the difference between babel-core and @babel/core?

Babeljs Problem Overview

Babeljs Solutions

Solution 1 - Babeljs

Make AppBar transparent and show background image which is set to whole screen

Java 11 application as lightweight docker image

Attributions