I am attempting upgrade to Webpack 4 to Webpack 5. However when I run npm start I get this error. Funny thing is I don't use applyWebpackOptionsDefaults anywhere and after scouring the node_modules I see that it is used in the webpack lib quite a few times. Can anyone tell me what I am doing wrong? Is there a package I haven't updated? What am I missing?
Failed to compile.
Invalid configuration object. Webpack has been initialized using a configuration object
that does not match the API schema.
configuration has an unknown property 'applyWebpackOptionsDefaults'. These properties are valid:
object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry?,
experiments?, externals?, externalsPresets?, externalsType?, ignoreWarnings?, infrastructureLogging?, loader?, mode?, module?, name?, node?, optimization?, output?, parallelism?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, snapshot?, stats?, target?, watch?, watchOptions? }
-> Options object as provided by the user.
For typos: please correct them.
For loader options: webpack >= v2.0.0 no longer allows custom properties in configuration.
Loaders should be updated to allow passing options via loader options in module.rules.
Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:
plugins: [
new webpack.LoaderOptionsPlugin({
// test: /.xxx$/, // may apply this only for some modules
options: {
applyWebpackOptionsDefaults: …
}
})
]
webpack.config.dev.js file:
const autoprefixer = require('autoprefixer');
const path = require('path');
const webpack = require('webpack');
const HtmlWebpackPlugin = require('html-webpack-plugin');
const CaseSensitivePathsPlugin = require('case-sensitive-paths-webpack-plugin');
const InterpolateHtmlPlugin = require('react-dev-utils/InterpolateHtmlPlugin');
const WatchMissingNodeModulesPlugin = require('react-dev-utils/WatchMissingNodeModulesPlugin');
const eslintFormatter = require('react-dev-utils/eslintFormatter');
const ModuleScopePlugin = require('react-dev-utils/ModuleScopePlugin');
const ProgressBarPlugin = require('progress-bar-webpack-plugin');
const getClientEnvironment = require('./env');
const paths = require('./paths');
// Webpack uses `publicPath` to determine where the app is being served from.
// In development, we always serve from the root. This makes config easier.
const publicPath = '/';
// `publicUrl` is just like `publicPath`, but we will provide it to our app
// as %PUBLIC_URL% in `index.html` and `process.env.PUBLIC_URL` in JavaScript.
// Omit trailing slash as %PUBLIC_PATH%/xyz looks better than %PUBLIC_PATH%xyz.
const publicUrl = '';
// Get environment variables to inject into our app.
const env = getClientEnvironment(publicUrl);
// This is the development configuration.
// It is focused on developer experience and fast rebuilds.
// The production configuration is different and lives in a separate file.
module.exports = {
// You may want 'eval' instead if you prefer to see the compiled output in DevTools.
// See the discussion in https://github.com/facebookincubator/create-react-app/issues/343.
context: __dirname + '/src',
devtool: 'cheap-module-source-map',
// devServer: {
// inline: false,
// contentBase: '../dist',
// },
// These are the "entry points" to our application.
// This means they will be the "root" imports that are included in JS bundle.
// The first two entry points enable "hot" CSS and auto-refreshes for JS.
entry: [
// We ship a few polyfills by default:
require.resolve('./polyfills'),
// Include an alternative client for WebpackDevServer. A client's job is to
// connect to WebpackDevServer by a socket and get notified about changes.
// When you save a file, the client will either apply hot updates (in case
// of CSS changes), or refresh the page (in case of JS changes). When you
// make a syntax error, this client will display a syntax error overlay.
// Note: instead of the default WebpackDevServer client, we use a custom one
// to bring better experience for Create React App users. You can replace
// the line below with these two lines if you prefer the stock client:
// require.resolve('webpack-dev-server/client') + '?/',
// require.resolve('webpack/hot/dev-server'),
require.resolve('react-dev-utils/webpackHotDevClient'),
// Finally, this is your app's code:
paths.appIndexJs,
// We include the app code last so that if there is a runtime error during
// initialization, it doesn't blow up the WebpackDevServer client, and
// changing JS code would still trigger a refresh.
],
output: {
// Add /* filename */ comments to generated require()s in the output.
pathinfo: true,
// This does not produce a real file. It's just the virtual path that is
// served by WebpackDevServer in development. This is the JS bundle
// containing code from all our entry points, and the Webpack runtime.
filename: 'static/js/bundle.js',
// There are also additional JS chunk files if you use code splitting.
chunkFilename: 'static/js/[name].chunk.js',
// This is the URL that app is served from. We use "/" in development.
publicPath: publicPath,
// Point sourcemap entries to original disk location (format as URL on Windows)
devtoolModuleFilenameTemplate: info =>
path.resolve(info.absoluteResourcePath).replace(/\\/g, '/'),
},
externals: {
'node-fetch': 'fetch',
},
resolve: {
// This allows you to set a fallback for where Webpack should look for modules.
// We placed these paths second because we want `node_modules` to "win"
// if there are any conflicts. This matches Node resolution mechanism.
// https://github.com/facebookincubator/create-react-app/issues/253
modules: ['node_modules', paths.appNodeModules].concat(
// It is guaranteed to exist because we tweak it in `env.js`
process.env.NODE_PATH.split(path.delimiter).filter(Boolean),
),
// These are the reasonable defaults supported by the Node ecosystem.
// We also include JSX as a common component filename extension to support
// some tools, although we do not recommend using it, see:
// https://github.com/facebookincubator/create-react-app/issues/290
// `web` extension prefixes have been added for better support
// for React Native Web.
extensions: ['.web.js', '.mjs', '.js', '.json', '.web.jsx', '.jsx'],
alias: {
react: path.resolve('node_modules/react'),
'react-dom': path.resolve('node_modules/react-dom'),
// Support React Native Web
// https://www.smashingmagazine.com/2016/08/a-glimpse-into-the-future-with-react-native-for-web/
'react-native': 'react-native-web',
'adp-react-components': path.resolve('node_modules/adp-react-components'),
},
plugins: [
// Prevents users from importing files from outside of src/ (or node_modules/).
// This often causes confusion because we only process files within src/ with babel.
// To fix this, we prevent you from importing files out of src/ -- if you'd like to,
// please link the files into your node_modules/ and let module-resolution kick in.
// Make sure your source files are compiled, as they will not be processed in any way.
new ModuleScopePlugin(paths.appSrc, [paths.appPackageJson]),
],
},
module: {
strictExportPresence: true,
rules: [
// TODO: Disable require.ensure as it's not a standard language feature.
// We are waiting for https://github.com/facebookincubator/create-react-app/issues/2176.
// { parser: { requireEnsure: false } },
// First, run the linter.
// It's important to do this before Babel processes the JS.
{
test: /\.(js|jsx|mjs)$/,
enforce: 'pre',
use: [
{
options: {
formatter: eslintFormatter,
eslintPath: require.resolve('eslint'),
},
loader: require.resolve('eslint-loader'),
},
],
include: paths.appSrc,
},
{
test: /\.(graphql|gql)$/,
include: paths.appSrc,
loader: 'graphql-tag/loader',
},
{
// "oneOf" will traverse all following loaders until one will
// match the requirements. When no loader matches it will fall
// back to the "file" loader at the end of the loader list.
oneOf: [
// "url" loader works like "file" loader except that it embeds assets
// smaller than specified limit in bytes as data URLs to avoid requests.
// A missing `test` is equivalent to a match.
{
test: [/\.bmp$/, /\.gif$/, /\.jpe?g$/, /\.png$/],
loader: require.resolve('url-loader'),
options: {
limit: 10000,
name: 'static/media/[name].[hash:8].[ext]',
},
},
{
test: /\.woff$/,
loader: 'file-loader',
options: {
name: '[name].[ext]',
outputPath: './fonts/',
publicPath: '',
},
},
// Process JS with Babel.
{
test: /\.(js|jsx|mjs)$/,
include: paths.appSrc,
loader: require.resolve('babel-loader'),
options: {
// This is a feature of `babel-loader` for webpack (not Babel itself).
// It enables caching results in ./node_modules/.cache/babel-loader/
// directory for faster rebuilds.
cacheDirectory: true,
},
},
// "postcss" loader applies autoprefixer to our CSS.
// "css" loader resolves paths in CSS and adds assets as dependencies.
// "style" loader turns CSS into JS modules that inject <style> tags.
// In production, we use a plugin to extract that CSS to a file, but
// in development "style" loader enables hot editing of CSS.
{
test: /\.css$/,
use: [
require.resolve('style-loader'),
{
loader: require.resolve('css-loader'),
options: {
importLoaders: 1,
},
},
{
loader: require.resolve('postcss-loader'),
options: {
// Necessary for external CSS imports to work
// https://github.com/facebookincubator/create-react-app/issues/2677
ident: 'postcss',
plugins: () => [
require('postcss-flexbugs-fixes'),
autoprefixer({
browsers: [
'>1%',
'last 4 versions',
'Firefox ESR',
'not ie < 9', // React doesn't support IE8 anyway
],
flexbox: 'no-2009',
}),
],
},
},
],
},
// JSON is not enabled by default in Webpack but both Node and Browserify
// allow it implicitly so we also enable it.
{
test: /\.json$/,
loader: 'json',
},
// "file" loader makes sure those assets get served by WebpackDevServer.
// When you `import` an asset, you get its (virtual) filename.
// In production, they would get copied to the `build` folder.
// This loader doesn't use a "test" so it will catch all modules
// that fall through the other loaders.
{
// Exclude `js` files to keep "css" loader working as it injects
// its runtime that would otherwise processed through "file" loader.
// Also exclude `html` and `json` extensions so they get processed
// by webpacks internal loaders.
exclude: [
/\.(js|jsx|mjs)$/,
/\.html$/,
/\.json$/,
/\.(graphql|gql)$/,
],
loader: require.resolve('file-loader'),
options: {
name: 'static/media/[name].[hash:8].[ext]',
},
},
],
},
// ** STOP ** Are you adding a new loader?
// Make sure to add the new loader(s) before the "file" loader.
],
},
plugins: [
// Makes some environment variables available in index.html.
// The public URL is available as %PUBLIC_URL% in index.html, e.g.:
// <link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico">
// In development, this will be an empty string.
new InterpolateHtmlPlugin(env.raw),
// Generates an `index.html` file with the <script> injected.
new HtmlWebpackPlugin({
inject: true,
template: paths.appHtml,
}),
// Add module names to factory functions so they appear in browser profiler.
// new webpack.NamedModulesPlugin(),
// Makes some environment variables available to the JS code, for example:
// if (process.env.NODE_ENV === 'development') { ... }. See `./env.js`.
// new webpack.DefinePlugin(env.stringified),
new webpack.DefinePlugin({ 'process.env.NODE_ENV': env.stringified }),
// This is necessary to emit hot updates (currently CSS only):
new webpack.HotModuleReplacementPlugin(),
// Watcher doesn't work well if you mistype casing in a path so we use
// a plugin that prints an error when you attempt to do this.
// See https://github.com/facebookincubator/create-react-app/issues/240
new CaseSensitivePathsPlugin(),
// If you require a missing module and then `npm install` it, you still have
// to restart the development server for Webpack to discover it. This plugin
// makes the discovery automatic so you don't have to restart.
// See https://github.com/facebookincubator/create-react-app/issues/186
new WatchMissingNodeModulesPlugin(paths.appNodeModules),
// Moment.js is an extremely popular library that bundles large locale files
// by default due to how Webpack interprets its code. This is a practical
// solution that requires the user to opt into importing specific locales.
// https://github.com/jmblog/how-to-optimize-momentjs-with-webpack
// You can remove this if you don't use Moment.js:
new webpack.IgnorePlugin({
resourceRegExp: /^\.\/locale$/,
resourceRegExp: /moment$/,
}),
new ProgressBarPlugin(),
new webpack.LoaderOptionsPlugin({
options: {
applyWebpackOptionsDefaults: {},
},
}),
],
// Some libraries import Node modules but don't use them in the browser.
// Tell Webpack to provide empty mocks for them so importing them works.
node: {
dgram: 'empty',
fs: 'empty',
net: 'empty',
tls: 'empty',
child_process: 'empty',
},
// Turn off performance hints during development because we don't do any
// splitting or minification in interest of speed. These warnings become
// cumbersome.
performance: {
hints: false,
},
mode: env.raw.NODE_ENV || 'development',
optimization: {
checkWasmTypes: false,
chunkIds: 'named',
concatenateModules: false,
emitOnErrors: true,
flagIncludedChunks: false,
mangleExports: false,
minimize: false,
moduleIds: 'named',
nodeEnv: 'development',
occurrenceOrder: false,
removeAvailableModules: false,
splitChunks: {
hidePathInfo: false,
minSize: 10000,
maxAsyncRequests: Infinity,
maxInitialRequests: Infinity,
},
},
};
Here is the package.json:
{
"name": "project",
"version": "1.0.827-beta.0",
"private": true,
"homepage": "/home",
"dependencies": {
"apollo-cache-inmemory": "^1.6.6",
"apollo-client": "^2.6.10",
"apollo-link": "^1.2.14",
"apollo-link-context": "^1.0.20",
"apollo-link-error": "^1.1.13",
"apollo-link-http": "^1.5.17",
"apollo-link-logger": "^1.2.3",
"apollo-link-state": "^0.4.2",
"chalk": "1.1.3",
"dotenv": "4.0.0",
"dotenv-expand": "4.2.0",
"flow-bin": "^0.122.0",
"fontawesome": "^4.7.2",
"fs-extra": "3.0.1",
"graphql": "^15.0.0",
"graphql-tag": "^2.10.3",
"highcharts": "^7.1.1",
"isomorphic-fetch": "^2.2.1",
"lodash": "^4.17.15",
"moment": "^2.24.0",
"nanoid": "^2.0.2",
"node-fetch": "^2.6.0",
"object-assign": "4.1.1",
"postcss-flexbugs-fixes": "3.2.0",
"promise": "8.0.1",
"prop-types": "^15.7.2",
"raf": "3.4.0",
"react": "^17.0.1",
"react-apollo": "2.5.8",
"react-copy-to-clipboard": "^5.0.1",
"react-dev-utils": "^11.0.1",
"react-dom": "^17.0.1",
"react-dropzone": "^4.3.0",
"react-fast-compare": "^2.0.4",
"react-mailto": "^0.4.0",
"react-quill": "^1.3.1",
"react-redux": "^5.0.7",
"react-router": "^5.2.0",
"react-select": "^2.0.0",
"react-show-more-text": "1.3.0",
"redux": "^4.0.0",
"redux-immutable-state-invariant": "^2.1.0",
"redux-thunk": "^2.3.0",
"resolve": "1.6.0",
"uniqid": "5.0.3",
"url-loader": "0.6.2",
"victory": "^0.24.2",
"victory-core": "21.1.3",
"xlsx": "^0.14.3"
},
"scripts": {
"boot:start": "cd ../../ && npm run bootstrap:f && cd packages/client && npm start",
"build": "node --max_old_space_size=4096 scripts/build.js",
"i": "npm install",
"regenlock": "npm install --package-lock",
"scorch": "rmdir \"node_modules\" /S /Q && del \"package-lock.json\" /S /Q",
"start": "node scripts/start.js",
"test": "jest --runInBand --coverage",
"write:tests": "jest --watchAll --runInBand",
"flow": "flow"
},
"devDependencies": {
"#apollo/react-testing": "^3.1.4",
"#babel/core": "^7.7.7",
"#babel/plugin-proposal-class-properties": "^7.8.3",
"#babel/plugin-transform-runtime": "^7.8.3",
"#babel/polyfill": "^7.7.0",
"#babel/preset-env": "^7.7.7",
"#babel/preset-react": "^7.7.4",
"autoprefixer": "7.1.6",
"babel-jest": "^24.9.0",
"babel-loader": "^8.0.6",
"babel-plugin-transform-flow-strip-types": "^6.22.0",
"case-sensitive-paths-webpack-plugin": "^2.3.0",
"css-loader": "0.28.7",
"enzyme": "^3.11.0",
"enzyme-adapter-react-16": "^1.15.2",
"eslint-loader": "^2.1.0",
"expect": "^1.20.2",
"extract-text-webpack-plugin": "^3.0.2",
"file-loader": "1.1.5",
"handlebars": "^4.7.1",
"html-webpack-plugin": "^4.5.1",
"jest": "^24.9.0",
"jest-junit": "^10.0.0",
"jest-transform-graphql": "^2.1.0",
"jsdom": "11.11.0",
"json-loader": "^0.5.7",
"postcss-loader": "2.0.8",
"precommit": "^1.2.2",
"progress-bar-webpack-plugin": "^2.1.0",
"redux-mock-store": "^1.5.4",
"style-loader": "0.19.0",
"sw-precache-webpack-plugin": "^1.0.0",
"url-loader": "0.6.2",
"webpack": "^5.17.0",
"webpack-cli": "^4.4.0",
"webpack-dev-server": "^3.11.2",
"webpack-manifest-plugin": "^3.0.0",
"whatwg-fetch": "2.0.3"
}
}
You need to fix scripts/start.js file.
There is a line in this file:
const compiler = createCompiler(webpack, config, appName, urls, useYarn);
You need to change it to
const compiler = createCompiler({ webpack, config, appName, urls, useYarn });
This change will fix your current error but probably you'll get the next one :)
new webpack.LoaderOptionsPlugin({
options: {
applyWebpackOptionsDefaults: {},
From your code...
Try updating your node part for webpack 5 as well. What was
node: {
dgram: 'empty',
fs: 'empty',
net: 'empty',
tls: 'empty',
child_process: 'empty',
}
has to be under resolve.fallback.
Source: https://webpack.js.org/migrate/5/#clean-up-configuration
Desired Behaviour
I want to be able to:
Use webpack to define a build process that uses babel to convert an ES6 server side Node file to "plain javascript"
Current Behaviour
If I just run:
node app.js
I get import errors:
import express from "express";
^^^^^^^
SyntaxError: Unexpected identifier
What I've Tried
When I try and define a build process in webpack, I get errors like:
Can't resolve
tls/net/fs/dns/child_process/aws-sdk/./local_settings/npm/node-gyp
There is a possible solution offered here, but it doesn't resolve all errors (these errors remain: aws-sdk, ./local_settings, npm, node-gyp):
target: "node"
There are also warnings like:
Module parse failed: Unexpected token
Critical dependency: the request of a dependency is an expression
This "how do I use ES6 in production?" question seems to be common, eg:
NodeJS in ES6/ES7, how do you do it in production?
Quickstart guide to using ES6 with Babel, Node and IntelliJ
Getting ready for production use
Is it okay to use babel-node in production
but none of the answers I have found seem definitive or specifically relate to a webpack solution.
Below is code I have now:
from webpack.config.js
const path = require('path');
console.log("the __dirname is: " + __dirname);
module.exports = {
entry: "./src/js/app.js",
output: {
filename: "app.js",
path: path.resolve(__dirname, "dist/js")
},
target: "node",
mode: "development",
module: {
rules: [{
test: /\.js$/,
exclude: /(node_modules)/,
use: {
loader: "babel-loader",
options: {
presets: ["env", "stage-0"]
}
}
},
{
test: /\.css$/,
use: [
{ loader: "style-loader" },
{ loader: "css-loader" }
]
},
{
test: /\.less$/,
use: [
{ loader: "style-loader" },
{ loader: "css-loader" },
{ loader: "less-loader" }
]
},
{
test: /\.jpg$/,
use: [
{ loader: "url-loader" }
]
}
]
}
}
from package.json:
...
"main": "app.js",
"scripts": {
"start": "nodemon ./app.js --exec babel-node -e js",
"build": "webpack",
"watch": "webpack --w"
},...
"dependencies": {
"bcrypt": "^2.0.1",
"body-parser": "^1.18.2",
"cors": "^2.8.4",
"express": "^4.16.3",
"jsonwebtoken": "^8.2.1",
"mongodb": "^3.0.8"
},
"devDependencies": {
"babel-cli": "^6.26.0",
"babel-core": "^6.26.3",
"babel-loader": "^7.1.4",
"babel-preset-env": "^1.7.0",
"babel-preset-stage-0": "^6.24.1",
"css-loader": "^0.28.11",
"file-loader": "^1.1.11",
"less": "^3.0.4",
"less-loader": "^4.1.0",
"style-loader": "^0.21.0",
"url-loader": "^1.0.1",
"webpack": "^4.8.3",
"webpack-cli": "^2.1.3"
}
Question
What should my webpack.config.js and package.json files look like in order to successfully convert the ES6 file to "plain javascript"?
By default, Webpack tries to bundle everything into a single .js file. For client-side projects this is fine, but for NodeJS projects it becomes slightly more complicated because you are including code from node_modules as well. Sometimes that can cause errors like the one you're seeing here.
What you want to do in addition to targets: "node" is tell Webpack not to bundle external dependencies (i.e. node_modules).
There's a useful library called webpack-node-externals that helps with this:
var nodeExternals = require('webpack-node-externals');
...
module.exports = {
...
target: 'node', // in order to ignore built-in modules like path, fs, etc.
externals: [nodeExternals()], // in order to ignore all modules in node_modules folder
...
};
So it's not really about "plain javascript", more like trying to get Webpack to output a file which is compatible with the NodeJS ecosystem.
I am trying to setup a new project and am having a bit of trouble with webpack-dev-server, it looks like the client compiles successfully but I cannot view the index.html or the main.js, they just dont seem to be available.
I have tried a bunch of different webpack config setups but none of them seem to work.
I have a project which has a client and a server directory, my folder structure looks like:
> project
> dist
> src
> client
client.tsx
webpack.config.js
> server
package.json
In package.json I have a dev client script: "dev-client": "cd ./src/client && webpack-dev-server -w",
my webpack.config.js looks something like this (i have changed it around quite a bit trying to get this to work):
const path = require("path");
const HtmlWebpackPlugin = require("html-webpack-plugin");
const projectRoot = path.join(__dirname, "..", "..");
module.exports = {
devtool: "inline-source-map",
mode: "development",
entry: "./client",
output: {
path: path.join(projectRoot, "dist", "public"),
publicPath: "/public/",
},
resolve: {
extensions: [".js", ".ts", ".tsx"],
},
module: {
rules: [
{
test: /\.tsx?$/,
use: {
loader: "ts-loader",
},
},
{
test: /\.scss$/,
use: [
{
loader: "style-loader",
},
{
loader: "css-loader",
},
{
loader: "sass-loader",
},
],
},
{
test: /\.(jpe?g|gif|png|svg|woff|woff2|ttf|eot)$/,
use: {
loader: "url-loader",
options: {
limit: 10000,
},
},
},
],
},
plugins: [
new HtmlWebpackPlugin(),
],
devServer: {
contentBase: path.join(projectRoot, "dist"),
},
}
When I run npm run dev-client I get the success message i ｢wdm｣: Compiled successfully. but when I navigate to http://localhost:8080/ all I see is the server which gets compiled to the dist folder.
Dependencies info:
"css-loader": "^0.28.11",
"file-loader": "^1.1.11",
"html-webpack-plugin": "^3.2.0",
"node-sass": "^4.9.0",
"sass-loader": "^7.0.1",
"style-loader": "^0.21.0",
"ts-loader": "^4.2.0",
"url-loader": "^1.0.1",
"webpack": "^4.6.0",
"webpack-cli": "^2.0.15",
"webpack-dev-server": "^3.1.3"
So after a bunch of testing I figured out that rolling back to 3.1.1 of webpack-dev-server fixed the issue, this lead me onto this issue:
https://github.com/webpack/webpack-dev-server/issues/1373
Which says that the issue is caused by spaces in the project path. I removed the spaces and it worked perfectly.
Posting here in case someone else has the same issue.
My webpack compilate is not transpiled into the right JS. It writes
exports default MultiLanguage
instead of
module.exports = { MultiLanguage: MultiLanguage};
My .bablerc
{
"presets": ["es2015", "stage-0"],
"plugins": ["transform-runtime"]
}
My package.json
{
"name": "myapp",
"version": "0.0.1",
"description": "My app",
"dependencies": {
"bootstrap": "^3.3.7",
"vue": "^2.4.2",
"vue-multilanguage": "^2.1.1"
},
"devDependencies": {
"babel-cli": "^6.24.1",
"babel-core": "^6.25.0",
"babel-loader": "^6.4.1",
"babel-plugin-transform-runtime": "^6.1.2",
"babel-preset-es2015": "^6.24.1",
"babel-preset-stage-0": "^6.1.2",
"babel-runtime": "^5.8.0",
"webpack": "^1.15.0"
},
"author": "You"
}
My webpack.config.js
module.exports = {
entry: './src/main.js',
output: {
path: './dist',
filename: 'build.js'
},
module: {
loaders: [
{
test: /\.js$/,
loader: 'babel',
exclude: /node_modules/
}
]
}
}
And therefor the error and the code where it hits in the build.js
in Chromium/Chrome und ubuntu:
Uncaught SyntaxError: Unexpected token export
in Firefox:
SyntaxError: export declarations may only appear at top level of a module
export default MultiLanguage
Here also the vue code (main.js):
import Vue from 'vue/dist/vue.js'
import MultiLanguage from 'vue-multilanguage/src/vue-multilanguage.js'
Vue.use(MultiLanguage, {
default: 'en',
en: {
hi: 'Hello',
welcome: 'Welcome, {name}'
},
pt: {
hi: 'Ola',
welcome: 'Bem-vindo, {name}'
}
})
any recommanded tutorials? any idea?
when I replace the line in build.js wit module.exports = { MultiLanguage: MultiLanguage}; the error does not occure
Your problem is linked to your import.
vue-multilanguage.js is not provided pre-compiled by its author (which is rare, usually libraries include a dist file ready to be used...) and as it is in your node_modules folder, it is not transformed from ES6 to ES5 by your babel loader as well. You need to add an exception in your webpack.config.js.
module.exports = {
entry: './src/main.js',
output: {
path: './dist',
filename: 'build.js'
},
module: {
loaders: [
{
test: /\.js$/,
loader: 'babel-loader',
// exclude everything from node_modules, except vue-multilanguage
exclude: /node_modules(?![\\/]vue-multilanguage[\\/])/
}
]
}
}
Not directly related, but not that I also replaced 'babel' by 'babel-loader', to avoid some bugs with older packages. See here.
Also, you can (and you probably should), as mentioned in the comments, import vue this way.
import Vue from 'vue';
Side note:
According to their package.json, there should be a file ready to be used in their library, located at dist/vue-multilanguage.js. But they oddly added their dist folder into their .npmignore file, and so it's not included. That's probably an error. I'll post an issue on their github. Once it's corrected, and if you update your package, you should be able to simply import vue-multi like this (without adding any exception to your webpack config):
import MultiLanguage from 'vue-multilanguage'
I would use next imports:
import Vue from './vue';
import MultiLanguage from './vue-multilanguage';
Basically, module loading is a pain in JavaScript right now sigh...
So I have a TypeScript application I'd like to be compiled with webpack. The issue is that my editor (vscode) seems to expect that modules are imported without extensions. For example:
import {IServer} from "../server/server";
In webpack, I can only get this to work if I include an extension. If I include an extension (i.e. "../server/server.ts") it builds in webpack, but the editor doesn't recognize it and throws an error that the module wasn't found. If I omit an extension (i.e. "../server/server"), webpack won't load it (it says it can't find the module "../server/server"), but the editor will load it for purposes of code-completion, etc.
This leads me to believe that importing modules in TypeScript are expected to be done without extensions, whereas in the webpack ecosystem, they are required (which makes sense with how loaders work, etc).
This leaves a very bad taste in my mouth. My question here is: is my conclusion correct? Do I have to trade off between the build system or the editor? Or am I missing something? Is it possible to have the webpack typescript loader silently add in the extensions so the modules are properly recognized by webpack during the build?
I have the following webpack.config.js file:
module.exports = [
{
name: "Server",
entry: "./src/server/server.ts",
output: {
filename: "./server/server.js"
},
target: "node",
resolve: [".ts", ".js"],
module: {
loaders: [
{ test: /\.ts$/, loader: 'ts-loader' }
]
}
},
{
name: "Client",
entry: "./src/client/scripts/client.ts",
output: {
filename: "./public/scripts/client.js"
},
resolve: ["", ".ts", ".js", ".less"],
module: {
loaders: [
{ test: /\.ts$/, loader: 'ts-loader' },
{ test: /\.less$/, loader: "style!css!less" },
{ test: /\.woff(2)?(\?v=[0-9]\.[0-9]\.[0-9])?$/, loader: "url-loader?limit=10000&minetype=application/font-woff" },
{ test: /\.(ttf|eot|svg)(\?v=[0-9]\.[0-9]\.[0-9])?$/, loader: "file-loader" },
{ test: /\.png$/, loader: "url-loader?mimetype=image/png" }
]
}
}
];
And the following tsconfig file:
{
"compilerOptions": {
"target": "ES5",
"module": "commonjs",
"jsx": "react"
},
"files": [
"src/shared/typings/tsd.d.ts",
"src/shared/typings/webpack.d.ts"
]
}
And I'm using the following packages in node:
"babel-core": "^6.2.1",
"babel-loader": "^6.2.0",
"babel-preset-es2015": "^6.1.18",
"css-loader": "^0.23.0",
"file-loader": "^0.8.5",
"less": "^2.5.3",
"less-loader": "^2.2.1",
"react-hot-loader": "^1.3.0",
"style-loader": "^0.13.0",
"ts-loader": "^0.7.1",
"typescript": "^1.6.2",
"url-loader": "^0.5.7",
"webpack-dev-server": "^1.12.1",
"moment": "^2.10.6"
is my conclusion correct
No. Extensions should definitely not be there.
Fix
resolve: [".ts", ".js"],
Should be :
resolve: {
extensions: ['.ts', '.js']
},
When in doubt, check the tests : https://github.com/TypeStrong/ts-loader/tree/master/test
in webpack, I can only get this to work if I include an extension.
Definitely not needed.
whereas in the webpack ecosystem, they are required
No again. They are not required.
entry: "./src/server/server.ts",
This should be entry: "./src/server/server". Also checkout the extensive list of tests https://github.com/TypeStrong/ts-loader/tree/master/test
I overcame all the compiling issues and created a project template here, https://github.com/c9s/ts-webpack
You can just clone the project to start without fighting with the config files...