-
Notifications
You must be signed in to change notification settings - Fork 175
[deprectable] #137
Comments
As it turns out, I MUST use the unminified version of your JS. It would be really nice if you renamed it. When I use
When I use I have RequireJS doing its own uglify2 while building a single You could try to track down the error yourself, but it might just be something that you recommend people use the .js file instead. RequireJS Mismatch page Is there any reason you don't just name the ts output
I'm realizing your js file probably isn't "deprecated" as I was guessing... since it's actually just an interim build file. |
@whatllb hello o/ i was reading your issue and i don't recommend that [deprectable] version, because it was the last code used, before being re-written in typescript. with your last post, i do agree that in some environments it's common to minify external components/plugins. i'll get it done asap :) sorry for the delay |
Cool. I appreciate the help. Do you have an interim .js file from the ts build that you're going to surface along with the minified version? Thanks. |
- added a file that's not minified. - updated [deprectable]angular.intro.js to angular-intro.deprectable.js to the standard format.
sure, it's on that PR, the file is available on "build/angular.intro.js" i had to update the version accordingly or it could break someone's build :) may you please check on your environment before we merge? i'll be grateful 😄 |
- added a file that's not minified. - updated [deprectable]angular.intro.js to angular-intro.deprectable.js to the standard format.
- added a file that's not minified. - updated [deprectable]angular.intro.js to angular-intro.deprectable.js to the standard format.
Hello again, sorry for not answer before :x but i did make a beta release with this fix: https://github.com/mendhak/angular-intro.js/releases/tag/v4.0.0-beta with this version i hope we can check the problem and see if you noticed something that we can improve |
I downloaded your zip file and saw the build/angular-intro.js file, and that the dependency is now IntroJs. |
The filename "src/[deprectable]angular-intro.js" is causing problems.
I'm trying to run your source version so I can debug an issue and help you. There's other dev reasons I might want to run your source version in the future.
I'm fighting with gulp to accept your filename "src/[deprectable]angular-intro.js".
I'm trying a normal operation and it really doesn't like the []'s. I can't even rename it. This should work, but I can't figure out if/how to escape the braces for gulp.
This would a lot more standard if this satisfied your naming intention:
angular-intro.deprecated.js
For now I'll temporarily rename the file in the package I download.
"deprectable" is a strange word. Maybe you mean "deprecated"? If so, angular-intro.deprecated.js might be a better choice. It would keep the standard filename prefix for your module and make it easier to manage copying them around (it would also mimic the intent of the file, like "min" does). For instance, I copy select module files into a "thirdparty" directory rather than deploying my "node_modules" directory. If I needed that src js file, then your project would be the only npm module I have with files that aren't prefixed by the module name. My gulpfile contains lots of lines like this, and I'm sure they don't collide with each other in thirdparty/js:
The text was updated successfully, but these errors were encountered: