Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook
Devcon 2020 Goes Virtual! LEARN MORE >

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

node_modules publishes every file EVERY time I publish anything

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    node_modules publishes every file EVERY time I publish anything

    Is there a way to exclude the node_modules folder from publishing each and every time I publish anything? I've got over 2200 files in node_modules. Even if I just edit a single a5w page, the entire node_modules tree gets published. Shouldn't they only publish if there's been a change to the files?


    Untitled.png
    Tags: node, publish
    #2
    Re: node_modules publishes every file EVERY time I publish anything

    When you select publish from the control panel it should pull up a full screen publishing view with all the publishing options.

    The option you want most is likely "publish new or modified files only."

    There is also a "publish selected only" option.

    Try them out, you'll like them!

    Comment

      #3
      Re: node_modules publishes every file EVERY time I publish anything

      Originally posted by lgrupido View Post
      The option you want most is likely "publish new or modified files only."
      I'm aware of this option. It is also enabled. All the files still get published each and every time.

      Originally posted by lgrupido View Post
      There is also a "publish selected only" option.
      I don't want to use this option for normal publishing because I want it to publish related components and files needed for whatever I'm publishing.

      Comment

        #4
        Re: node_modules publishes every file EVERY time I publish anything

        When you use the publish selected only option, it will still publish security files and other absolute necessities, but it won't publish embedded components and the like.

        But when you need that, just turn the option off one time, publish everything, then turn it back on.

        You should seriously give it a try.

        Comment

          #5
          Re: node_modules publishes every file EVERY time I publish anything

          Using that option, It still tries to publish 132 files, but at least that's better than 2200+

          Comment

            #6
            Re: node_modules publishes every file EVERY time I publish anything

            May I interject a secondary question? What is up with the vast number of "node" files anyway and how can a system with so many files be managed? I've been watching the number of files and folders in Alpha's "node_modules" folder increase at alarming rates. Here's a list of Alpha Build numbers and the resulting count of files and folders in the "node_modules" folder:

            Build 2580 - 5,439
            Build 3446 - 14,163
            Build 3670 - 14,207
            Build 3962 - 23,732
            Build 4119 - 24,062

            Comment

              #7
              Re: node_modules publishes every file EVERY time I publish anything

              Originally posted by RichCPT View Post
              May I interject a secondary question? What is up with the vast number of "node" files anyway and how can a system with so many files be managed? I've been watching the number of files and folders in Alpha's "node_modules" folder increase at alarming rates. Here's a list of Alpha Build numbers and the resulting count of files and folders in the "node_modules" folder:

              Build 2580 - 5,439
              Build 3446 - 14,163
              Build 3670 - 14,207
              Build 3962 - 23,732
              Build 4119 - 24,062
              Have you calculated how many different license files there are in these 24092 files?


              If you install Angular 2 you get 32000 files and with cli about 41000 files... "Hello world":)

              I remember I once tried to install some framework (maybe Material) and I did get 50000 files. I did not get it work. The lesson was that if installed nodejs app do not work then there is no way to figure it out why?

              Comment

                #8
                Re: node_modules publishes every file EVERY time I publish anything

                So those are two separate node_modules folder. The one you are talking about is installed by Alpha in both the dev and server environments. It is used for some of the third party integrations that xbasic provides, like Stripe, redis, etc.... This folder is NOT published to the server with your files because it already exists on the server.

                The node_modules folder I am talking about IS contained in my project files. I use it mostly for dependency management, but I will also be doing some AWS integration with it soon using my own node service. These files ARE published to the server because they exist in my project.

                See these videos for more info:
                http://www.ajaxvideotutorials.com/V1..._package_1.swf
                http://www.ajaxvideotutorials.com/V1..._package_2.swf
                http://www.ajaxvideotutorials.com/V1..._package_3.swf

                Edit: The reason there are so many files is because node's dependency structure. I would do some research into npm and how it structures dependencies to learn more.

                Comment

                  #9
                  Re: node_modules publishes every file EVERY time I publish anything

                  Originally posted by Sparticuz View Post
                  So those are two separate node_modules folder. The one you are talking about is installed by Alpha in both the dev and server environments. It is used for some of the third party integrations that xbasic provides, like Stripe, redis, etc.... This folder is NOT published to the server with your files because it already exists on the server.

                  The node_modules folder I am talking about IS contained in my project files. I use it mostly for dependency management, but I will also be doing some AWS integration with it soon using my own node service. These files ARE published to the server because they exist in my project.

                  See these videos for more info:
                  http://www.ajaxvideotutorials.com/V1..._package_1.swf
                  http://www.ajaxvideotutorials.com/V1..._package_2.swf
                  http://www.ajaxvideotutorials.com/V1..._package_3.swf

                  Edit: The reason there are so many files is because node's dependency structure. I would do some research into npm and how it structures dependencies to learn more.
                  Then do not put them to root. Use AA install folder instead (if classic server).

                  Comment

                    #10
                    Re: node_modules publishes every file EVERY time I publish anything

                    They need to be accessible to the browsers because they are css and js dependencies, that's why they are in the node folder in my project, not in the backend node folder from Alpha.

                    This is some kind of bug because nothing has changed on the files, yet they are republished each time. I didn't want to send a bug report because I wanted to verify that it's a bug first.

                    Comment

                    Previous template Next
                    Working...
                    X