disable minifing and bundling of the fornt end files

Flow
1

hi,

I am using

 <plugin>
                <groupId>com.vaadin</groupId>
                <artifactId>vaadin-maven-plugin</artifactId>
                <version>${vaadin.version}</version>
                <executions>
                    <execution>
                        <goals>
                            <goal>prepare-frontend</goal>
                            <goal>build-frontend</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

but I would like to disable the minify and bundling to better debug…

already tried:

<properties>
    <vaadin.minify>false</vaadin.minify>
	<vaadin.bundle>false</vaadin.bundle>
	<vaadin.hash>false</vaadin.hash>
</properties>

also tried:

<properties>
    <minify>false</minify>
	<bundle>false</bundle>
	<hash>false</hash>
</properties>

also tried…

 <plugin>
                <groupId>com.vaadin</groupId>
                <artifactId>vaadin-maven-plugin</artifactId>
                <version>${vaadin.version}</version>
                <executions>
                    <execution>
                        <goals>
                            <goal>prepare-frontend</goal>
                            <goal>build-frontend</goal>
                        </goals>
                    </execution>
                </executions>
                <configuration>
                    <generateBundle>false</generateBundle>
                </configuration>
            </plugin>

none worked though…

how should I do this?

thanks

2

Hi,

I think without changing the settings you can debug the javascript/css.

Are you running the application in production mode or development mode?

3

Perhaps your pom.xml is not correct.

In development mode you should have:


            <!--
                Take care of synchronizing java dependencies and imports in
                package.json and main.js files.
                It also creates webpack.config.js if not exists yet.
            -->
            <plugin>
                <groupId>com.vaadin</groupId>
                <artifactId>vaadin-maven-plugin</artifactId>
                <version>${vaadin.version}</version>
                <executions>
                    <execution>
                        <goals>
                            <goal>prepare-frontend</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

And production mode:

<profile>
            <!-- Production mode is activated using -Pproduction -->
            <id>production</id>
            <properties>
                <vaadin.productionMode>true</vaadin.productionMode>
            </properties>

            <dependencies>
                <dependency>
                    <groupId>com.vaadin</groupId>
                    <artifactId>flow-server-production-mode</artifactId>
                </dependency>
            </dependencies>

            <build>
                <plugins>
                    <plugin>
                        <groupId>com.vaadin</groupId>
                        <artifactId>vaadin-maven-plugin</artifactId>
                        <executions>
                            <execution>
                                <goals>
                                    <goal>build-frontend</goal>
                                </goals>
                                <phase>compile</phase>
                            </execution>
                        </executions>
                    </plugin>
                </plugins>
            </build>
        </profile>
4

but if in dev I use only prepare-frontend will it still work on IE11 ?

I was under the impression that build-fronted is the one that handles transpilation ans such.

5

Hi, I’m not sure if you need the production mode in vaadin 14 to use it in internet explorer. But I think it should work in dev . Are you trying to fix a bug which is only on internet explorer?