Lifetime Licenses I support wholeheartedly, but I hate the notion of different editions. Part bet, part investment, it made me wish more I recently purchased a lifetime hosting plan at TextDrive and it feltĭifferent. Lifetime ones, at (for example) 2 or 2.5 times the standard P.L. Next time you "offer" Personal License, what about also selling license is for "personal" version of IDEA (not Enterprise version, if Note: to avoid abuses, JetBrains could have to draw a line somewhere. You'd get direct injection of 1/ more money, from 2/ more buyers. Make a bet on JetBrains future and my need of Java, and pay 200-250% for I've already purchased 3 personal license in a row, and I'd be ready to No more "Do I buy it now", or do I wait 3 months till the next EAP, and babelrc with the custom root or alias.What, nobody catches on this idea? I see it as a real win-win, for Or yarn add -dev babel-plugin-module-resolver Install the plugin npm install -save-dev babel-plugin-module-resolver
Instead of that: const MyUtilFn = require( '././././utils/MyUtilFn')
And it also work with require calls // Use this: const MyUtilFn = require( 'utils/MyUtilFn') Instead of that: import MyUtilFn from '././././utils/MyUtilFn' Use this: import MyUtilFn from 'utils/MyUtilFn' It will allow you to work faster since you won't need to calculate how many levels of directory you have to go up before accessing the file. /././utils/my-utils, you can write utils/my-utils. For example, instead of using complex relative paths like. This plugin can simplify the require/import paths in your project. It also allows you to setup a custom alias for directories, specific files, or even other npm modules.
This plugin allows you to add new "root" directories that contain your modules. A Babel plugin to add a new resolver for your modules when compiling your code using Babel.
0 kommentar(er)
