Comments (7)
Since the module uses ES2015 arrow functions, it is not compatible with client side code. I believe Meteor.js is working to enable Babel for node modules, but we are not there yet.
Note that arrow functions are still slower than legacy functions... I don't know why everyone use it everywhere already.
from camelcase.
I'll let @sindresorhus respond to this (:
from camelcase.
Got same error
from camelcase.
Note that arrow functions are still slower than legacy functions...
No: https://kpdecker.github.io/six-speed/
from camelcase.
See: sindresorhus/ama#446
from camelcase.
@sindresorhus what do you mean "no"? The link you suggest shows that declarations are generally 1.4x slower! Thus, in the actual implementation, you are effectively declaring arrow functions 3 times. Therefore, my statement is completely valid.
But this is beside the main issue; this module cannot be used on client side as it does not provide a browser friendly source, and UglifyJS fails.
You closed this issue without addressing the real problem.
from camelcase.
The arrow
test shows it's identical. Even if it's 1.2x, that's pretty negligible in practice.
You closed this issue without addressing the real problem.
I linked to sindresorhus/ama#446. I don't have the time to answer this every time it comes up.
from camelcase.
Related Issues (20)
- NPM is not updated with the latest version HOT 1
- ts-jest encountered an unexpected token with camelcase HOT 2
- Must use import to load ES Module HOT 2
- pascal case broken when string ends with 1 number and 1 letter. HOT 2
- Cannot run tests: update the xo dependency to the latest (currently v0.54.2) HOT 2
- Error in Index.js in 6.0.0 version HOT 1
- Build break with camelcase 6.0.0 HOT 1
- Converted `c2d_f` value is `c2DF`? HOT 1
- Case conversion with specific locale HOT 3
- `preserveConsecutiveUppercase` option
- Converting either volume_3d or volume3d results in volume3D making it impossible to decamelize HOT 10
- Incorrect behaviour with numbers HOT 1
- Move regexes to the outer scope
- how to resolve this problem with /[\p{u}]/: Invalid escape? HOT 1
- version 6.2.1, build error HOT 1
- SyntaxError: Invalid regular expression: /[\p{Lu}]/: Invalid escape HOT 4
- "Invalid regular expression: /[\p{Lu}]/: Invalid escape" after updating to version 6.2.1 HOT 1
- "Invalid regular expression: /[\p{Lu}]/: Invalid escape" after updating to version 6.2.1 HOT 2
- "IDs" isn't camelized well HOT 3
- Passed in a single seperator, return the original seperator HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from camelcase.