The syntax that Sublime selects is based primarily on the extension that the file has. You can select View > Syntax > Open all with current extension as… from the menu while you have such a file open to tell Sublime what syntax you want it to use for any particular extension. If you sometimes … Read more
In my opinion, the best practice is to publish both minified code in dist folder and also the source code in src folder. One should also include other files such as package.json, package-lock.json, README.md, LICENSE.txt, CONTRIBUTING.md, etc which are at the root package directory. To achieve this, one should use files property in package.json to … Read more
In short, transpiling is an expensive process and many projects have thousands (if not hundreds of thousands) of lines of code imported in that babel would need to run over. Your node_modules should already be runnable without transpiling as said already and there are simple ways to exclude your node_modules but transpile any code that … Read more
Creating a babel.config.js with this script solve my issue module.exports = { presets:[ “@babel/preset-env”, “@babel/preset-react” ] }
Use this as your start point: var gulp = require(‘gulp’); var gutil = require(‘gulp-util’); var sourcemaps = require(‘gulp-sourcemaps’); var source = require(‘vinyl-source-stream’); var buffer = require(‘vinyl-buffer’); var browserify = require(‘browserify’); var to5ify = require(‘6to5ify’); var uglify = require(‘gulp-uglify’); gulp.task(‘default’, function() { browserify(‘./src/index.js’, { debug: true }) .transform(to5ify) .bundle() .on(‘error’, gutil.log.bind(gutil, ‘Browserify Error’)) .pipe(source(‘bundle.js’)) .pipe(buffer()) .pipe(sourcemaps.init({loadMaps: … Read more
To expand on veg_prog’s answer, you should use something like Browserify if you want to organize your code into modules. Browserify can be used with Grunt via grunt-browserify, and Babel can be used with Browserify via babelify. I’ve tweaked some of your files to show you how it can be done: index.html <!DOCTYPE html> <html> … Read more
That is how Browserify transforms work, transforms only have an effect directly in the module that is being referenced. If you want a module in node_modules to have a transform, you’d need to add a package.json to that module and add babelify as a transform for that module too. e.g. “browserify”: { “transform”: [ “babelify” … Read more
I solved this issue using: npm uninstall -g jest npm install -g jest npm cache clean npm install
All the solutions given here are correct. The easiest change is to just wrap your function call in a JSX element: return ( <div> { this.renderRecipeItems() } </div> ) However, none of the answers are (correctly) telling you why the code was breaking in the first place. For the sake of an easier example, let’s … Read more
Question: It feels like workaround, but isn’t there a more convenient way to handle such issues? I just pretend there will be more and more untransformed packages outside in the near future (following this discussion) and do we always have to manually put the package names for it in webpacks’ exclude rule?? You can use … Read more