Our company decided not to use webpack after doing a test run but we are still seeing the following screenshot in our browsers and the bundled files there are still causing issues. I dont see them anywhere on the filesystem
Does anyone know how or where this gets generated? I've commented out all of our webpack config files even the package json but its still there any thoughts? No process is running from what I can tell either.
I just found it we still had one of the webpack generated js files left and so on pages that called that generated file, all the the import statements were then being called and grabbing the src files as well. Hopefully that made sense but I've got the issue resolved.
Related
So I am using the following tutorial. I can access the localhost, but I am putting in an html file. The tutorial does not go into depth about setting up a javascript file and getting that file to transpile. Can someone help me with the setup. I have googled this topic and I keep coming across tutorials that talk about needing babel for the transpiling, yet the tutorial says
Now that everything’s ready to go, we can get webpack to watch for
code changes in our directory and transpile.
But I feel like this means it should just bundle up everything in my project since webpack is a bundling product. Further, I am confused by the call to webpack:
CMD webpack --watch --watch-polling
Does this mean I don't need to put in an entry point and endpoint? I thought with webpack I need to provide those two details, but the tutorial again is calling directly to just polling.
Thanks in advance for any help getting my structure setup so I can run webpack, react in docker.
In terms of setting up the files, I had to add
COPY wwwroot ./wwwroot
Just to get the project to display something at localhost. But I want files to be brought over automatically if possible. But I am not sure of the intent of the tutorial with regards to file structure.
I've been wasting a lot of time trying to learn how to deploy angular 2. I tried looking around how to do it on tomcat, because that's what I was ordered to do, but turns out tomcat isn't really used for this, is more java and jsp oriented, so I've read is better to use Apache HTTP server instead.
I just installed Apache server, and I just installed npm with gulp ( https://github.com/swirlycheetah/generator-angular2 ), and everything works fine: I can run my app on localhost:3030 with gulp but I now want to test it with Apache,
I've tried several things (since I haven't seen one single place explaining this, maybe it's a very basic thing to do?):
Configure apache .conf file to change the htdocs to a folder I've created. I've tested this works, I see the result on screen when I access localhost.
Compiled everything, got a folder called build with all my files changed to .js extention, so I figured, that must be it. I copied all the files in there, the lib folder created, and index.html and css files. Doesn't work.
Tried several combinations of picking some files that I figured would be necessary and not others. Doesn't work.
Copied the whole project that I've tested with gulp, with eclipse etc that works, including .ts and .d.ts files, which I've read shouldn't be there and are not necessary, and it works.
So I would like to know how is this really done, because I feel like I'm making no improvements. After reading post after post and blog after blog about I simply needed to transpile .ts files to .js, and simply put that javascript files on "some" folder the server uses, it would work. Not only it doesn't but when I use the original .ts files it does.
What might be going on and more important, how is this deployment (I guess it's called something else since I can't find much anything) properly done?
Make sure your .js file paths in your index.html page are correct. When you generate .js files in a folder(like build), your index.html may keep source paths for those .js files are like src="inline.js". So when you access index.html in build folder - localhost/build, it looks for those .js files in localhost only not localhost/build. Try to update source path of those .js files to /build/.
src="/build/inline.js".
you can do that using proxy option in Browser Sync..
proxy option link
I didn't try it but may be it will help you.
I have this app that seems to run normally on localhost but when I deployed it to meteor or digital ocean, then from sudden reason, no functionalities work...
Here is the screencast localy: http://screencast.com/t/tyD995EyM
Here is the current hosted version on meteor: cryptonic.meteor.com
And digital ocean: 104.236.90.81
Code repo on git if it helps... https://github.com/lklancir/cryptonic
Could anyone at least help me locate the problem or point in direction, no major console log errors...
I might be guessing that maybe some JS files are killing each other when composed in one single .js file on upload, but why does it work locally is the thing that bothers me
I do see this error in the console on the meteor.com site...
Uncaught ReferenceError: gnMenu is not defined
I'm not completely sure, but I think it might be a file loading order. You have client/lib/custom.js which uses gnMenu from client/lib/gnmenu.js
Since all files in lib are loaded first, there might be a load order issue. Per the http://docs.meteor.com/#/full/structuringyourapp page, the files should be loaded from lib in alphabetical order so this would be an issue as custom.js would be loaded first, but I do not know why it would work on local...
HTML template files are always loaded before everything else
Files beginning with main. are loaded last
Files inside any lib/ directory are loaded next
Files with deeper paths are loaded next
Files are then loaded in alphabetical order of the entire path
I love CodeKit, but for some reason, it stopped "watching" for changes to the files in the folder I placed in there. I double checked the project configuration to make sure the output paths are correct, but when I make a change to any of the files being watched, CodeKit does nothing -- no minifying, syntax checking, compiling down .scss files to .css.
As the developer suggested to "refresh" CodeKit, I launched the app while holding down shift and sure enough CodeKit opened with no projects. So I re-added the project, and still, it is not watching the files. Has anybody ever encountered this with CodeKit?
I have experienced a similar issue before and it was because in the codekit project I had included the images folder and I generated a huge amount of .png images. Every time codekit ran it got hung up processing the pngs trying to compress them.
Try putting your images folder outside of your codekit project directory and see if that helps.
I've been having the same problem lately (Version 2.1.9). I haven't managed to figure out the root cause as yet, but I have figured out a way to solve this issue every time it occurs.
Rename your parent folder that contains all of your CodeKit projects. E.g. my HTDocs equivalent folder is called "Sites". In Terminal do this:
mv sites sites_temp
mv sites_temp sites
The first line will rename your sites folder to sites_temp, and then the second line will do the opposite.
For some reason this works every time for me.
I've written a short blog post on this matter here, but to be honest the above is my go-to solution whenever this problem occurs: http://www.joetannorella.com/codekit-mac-auto-compiling-compass-upon-file-change/
I may just be doing something wrong but all of my javascript files as well as my css files are each individually available. This would be perfect except asset pipeline also adds my applicaion.js which is making my javascript crash. Is there a way that I can tell rails not to load all the individual files, I want JUST the application.js/css files.
As you can see here, the search and sort bars are shown twice because the javascript is trying to run twice. Anyone else deal with this? I have seen a couple other people ask this question and have yet to see a good answer.
IIRC this is caused by you having pre-compiled assets in public/assets, but having config.assets.compile set to true in the config for your current environment.
Normally if you're compiling assets on each request application.css and .js will only contain code that you have specifically entered into those files in app/assets, whereas if the assets have been pre-compiled (and are in public/assets) you'll see all your css and javascript in those files.
To fix this issue rm -rf public/assets and you should be good to go.