Require Outside Libraries

there Copy is now available: https://symfony.com/blog/en...

If you ever get a warning from Yarn like this:

An unexpected error occurred: "EPERM: operation not permitted, unlink '.....\\node_modules\\.bin\\encore'"

Before you try to install jquery, please stop encore. I spent quite a while figuring out why yarn couldn't delete node_modules/.bin/encore... on my Windows 10 machine. *Doh!*

Hey JAVroegop

Nice tip, thanks for sharing it :)
Cheers!

I need some help.

I want to add an external js lib in the right way. This js lib needs to be in the same scope as my code in my entry.
All I have is the link the link: <script src="https://sdk.example.api.js"></script>

What I tried:

1. Adding the scripttag in to my HTML don't work because everything in scripttags lands in globalspace and is not able see my code in my WP entry.
2. downloading the script and importing it : import '../api.js' does not work the script throws an errormessage that it's not allowed to run the script like this and that I should load it like this: <script src="https://sdk.example.api.js"></script>

I have no idea how the script knows how its loaded but is there anything I can do?

Hey Daniel W.

Your approach of downloading the JS file and then importing it is the right way but I believe the library you're trying to use was written a way that's not compatible with Webpack. As an example, there are some old jQuery plugins that cannot be used with Webpack

Cheers!

Hi! everyone, after installing the sweetalert2 plugin, i'm having this error in the browser. After followed along all the steps.
- Installation (yarn add sweetalert2 --dev)
- Removing the script tag from index.html.twig
- Removing the swal global variable from the function argments at the top and the bottom
- Adding the require line (const swal = require('sweetalert2');)

In chrome, i'm having this error:

Uncaught TypeError: Cannot read property 'constructor' of undefined
at SweetAlert (sweetalert2.all.js:2524)
at RepLogApp.handleRepLogDelete (RepLogApp.js:83)
at HTMLDivElement.dispatch (jquery-3.1.1.min.js:3)
at HTMLDivElement.q.handle (jquery-3.1.1.min.js:3)

In Firefox developer edition, i'm having this one:

TypeError: this is undefined[En savoir plus] rep_log.js line 21 > eval:2524:7
SweetAlert webpack:///./node_modules/sweetalert2/dist/sweetalert2.all.js?:2524
handleRepLogDelete webpack:///./public/assets/js/RepLogApp.js?:83
handleRepLogDelete self-hosted:974
jQuery 2

I've already checked on google, but I've just found something about a ".fire" function which is now available inside the "swal" object. Some said that it worked for them, but i'm so new to javascript, i don't even know where to put it in ryan's code. I've even try to install the same version on "jquery" and "sweetalert2" as him, but it doesn't change anything. I'm a symfony back-end developper (trying to become full-stack) and I'm just trying to start working with webpack since i know it's a great tool.

Don't know what to do. May i have a help please.

Thanks guys

Well, i eventually found out it was just a version matter. The version above 8 seems (Cause mine installed version "sweetalert2@8.2.4") to not be working properly. So i installed the exact same version as Ryan ("sweetalert2@7.12.0"), and it does.

You can also execute "yarn add sweetalert2@^7.11.0 --dev".

Thanks

Hey crgbe,

Thank you for getting back on this problem, it might be helpful for others.

Cheers!

Why is sweetalert2 installed with --dev? In Symfony, using composer the --dev makes sense for debug-pack, webserver, fixtures, etc. But SweetAlert (and jQuery, etc.) are using the final app, not just during development. Obviously, it works, but I'm uncertain about when something should be installed using --dev.

Hey Michael,

Good question! Actually, all your Node dependencies are dev because nothing of them is publicly available, right? Because node_modules/ as also assets/ folders are behind the server document root, i.e. outside of public/ folder. What to expose is up to you, and you do this with Webpack Encore that moves all the *prod* assets into the public/build/ folder that is available for everyone. So, technically ALL your Node packages that you install with npm/yarn are for *dev* only. But really, it is not important at all, you can move them all to the "dependencies" section and nothing will change. Really, you need to care about "devDependencies" and "dependencies" if you write a Node JS server application.

I hope it clarify things for you.

Cheers!

I'am trying to install a yarn plugin called: <a target="_blank" href="https://yarnpkg.com/en/package/autoprefixer&quot;&gt; autoprefixer </a>.
Autoprefixer auto fills css for different browsers.

In my webpack.config.js i've added:

    #webpack.config.js
    .addLoader({
        test: /\.css$/,
        use: ["style-loader", "css-loader", "postcss-loader"]
    })

In my backend.js i've added

    #assets/js/backend/backend.js
'use strict';

import $ from 'jquery';
import 'bootstrap';
import 'autoprefixer';

// rest of js code here
$(document).ready(function(){

});

But when i run yarn run encore dev --watch i get errors. Hope someone could help me out.

Webpack is watching the files…

 ERROR  Failed to compile with 2 errors                                                                                                                                                19:58:37

 error  in ./assets/scss/backend/backend.scss

Module build failed: 
'use strict';
^
      Invalid CSS after "'": expected 1 selector or at-rule, was "'use strict';"
      in /node_modules/autoprefixer/lib/autoprefixer.js (line 1, column 1)

 @ ./assets/scss/backend/backend.scss 4:14-211
 @ multi ./assets/scss/backend/backend.scss

 error  in ./assets/scss/backend/backend.scss

Module build failed: ModuleBuildError: Module build failed: 
'use strict';
^
      Invalid CSS after "'": expected 1 selector or at-rule, was "'use strict';"
      in /node_modules/autoprefixer/lib/autoprefixer.js (line 1, column 1)
    at runLoaders (/node_modules/webpack/lib/NormalModule.js:195:19)
    at newwayhoogeveen/node_modules/loader-runner/lib/LoaderRunner.js:364:11
    at /node_modules/loader-runner/lib/LoaderRunner.js:230:18
    at context.callback (/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at Object.asyncSassJobQueue.push [as callback] (/node_modules/sass-loader/lib/loader.js:76:13)
    at Object.done [as callback] node_modules/neo-async/async.js:7974:18)
    at options.error (node_modules/node-sass/lib/index.js:294:32)

Hey Bertin!

... not to ignore your question... but I might have a better solution for doing this. Encore already supports PostCss (just call enablePostCss) - I see you added this manually in your code, but this isn't necessary. PostCss (as I think you know) can be used to integrate with autoprefixer. In fact, if I remember correctly, when you call enablePostCss(), Encore will give you an error that you need to create a config file, and the config contents it suggests include the code needed to enable autoprefixer (you likely already have this config file). So basically, you add one line to webpack.config.js, add one config file, install a few packages (which Encore will tell you) and... that should be it!

Let me know if this helps!

Hey weaverryan
It works.
I just enabled enablePostCss() in webpack.config.js
When running yarn run encore dev --watch, i get the message package 'postcss-loader' missing.

After adding the package and run the comment again, it says: FIX create a postcss.config.js file.

I've created this file at the root

# at config, postcss.config.js 
module.exports = {
    plugins: {
        'autoprefixer': {},
    }
};

Now it works

And when i look in my compiled css
position: sticky; has now also position: -webkit-sticky; (created by autoPrefixer).

But i've some questions:

1. Now i need to add the postcss.config.js file to the root but is there a way to change the path, eq to /assets/configs/

I've seen some options on git, <a href="https://github.com/symfony/webpack-encore/pull/130&quot;&gt;webpack-encore pull 130</a>

But don't now how to use it within webpack.encore.js.
See my webpack.config.js below with an example but not working

var Encore = require('@symfony/webpack-encore');
const CopyWebpackPlugin = require('copy-webpack-plugin');

Encore
    .setOutputPath('public/build/')
    .setPublicPath('/build')
    .cleanupOutputBeforeBuild()
    .autoProvidejQuery()
    .enableSourceMaps(!Encore.isProduction())
    .enableVersioning()

    .createSharedEntry('js/common', ['jquery'])
    .addEntry('js/backend/backend', './assets/js/backend/backend.js')
    .addStyleEntry('css/backend/backend', ['./assets/scss/backend/backend.scss'])

    .addEntry('js/frontend/app', './assets/js/frontend/app.js')
    .addStyleEntry('css/frontend/app', ['./assets/scss/frontend/app.scss'])
    .addStyleEntry('css/frontend/login', './assets/scss/frontend/login.scss')

    .enableSassLoader()
    .enablePostCssLoader()

    .addPlugin(new CopyWebpackPlugin([
        // copies to {output}/static
        { from: './assets/static', to: 'img' }
    ]))
;

// example but not working
// Encore.enablePostCssLoader((options) => {
//     options.config = {
//         path: 'assets/config/'
//     };
// });

module.exports = Encore.getWebpackConfig();

Some other question, in the video about Copy image you mentioned that encore would have an copy feature in the future. Is this already being implemented?

Hey Bertin!

Woohoo! I'm so happy it's working! This is exactly the "workflow" I was hoping people would have to enable this feature :).

> 1. Now i need to add the postcss.config.js file to the root but is there a way to change the path, eq to /assets/configs/

Hmm. The commented-out config you have looks perfect. When you try this, do you get an error? Or does it just not see the file in the new location? If you completely move the file to the new location (and use that config), is there an error or does it just not work correctly? I'm not sure what's going wrong here.

> 2. Some other question, in the video about Copy image you mentioned that encore would have an copy feature in the future. Is this already being implemented?

Booo. No, not yet. Here's the PR: https://github.com/symfony/.... It's blocked due to some problems in an upstream library. I'm not sure if we'll be able to work around that, or if we'll just need to implement something ourself.

Cheers!